docs: cross-link vault-onboarding companion skill; add pkm keywords - #410
docs: cross-link vault-onboarding companion skill; add pkm keywords#410aliasunder wants to merge 12 commits into
Conversation
New Companion section mirrors the obsidian-vault one — vault-onboarding bootstraps the collaboration system this server powers, standalone or vault-cortex-connected. Its H2 joins EXCLUDED_H2 so it stays out of DOCKERHUB.md (regenerated: byte-identical). Keywords swap attachments for pkm + personal-knowledge-management, matching the GitHub topics update; LobeHub listing tags derive from keywords, so publish:lobehub needs a run after merge. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
umm-actually re-reviewed at No new findings (1 tracked finding(s) across all runs). Context notes
umm-actually · deepseek/deepseek-v4-flash-0731 |
|
Draft until vault-onboarding completes Stage 5 validation (install test + interview-path walkthroughs, planned for Fri/weekend) — the companion section shouldn't advertise the skill from this README while it's still pre-validation. Mark ready + merge once validation passes, then run 🤖 Generated with Claude Code |
Same pkm + personal-knowledge-management pair as the root package and GitHub topics — the CLI is the npm-facing surface where keywords power search, and the first organic community mention of vault-cortex came from r/PKMS. Goes live on the next CLI publish. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…rd-list conflicts)
![umm-actually[bot]](https://avatars.githubusercontent.com/in/4233716?s=60&v=4){kind=small}
| "second-brain", | ||
| "pkm", | ||
| "personal-knowledge-management", |
There was a problem hiding this comment.
Align PR description with the actual keyword change
Low severity · subtle bugs · high confidence
The PR description claims package.json keywords were changed as attachments → pkm + personal-knowledge-management (kept pdf), but the diff only adds second-brain to cli/package.json; attachments remains in the list and pkm/personal-knowledge-management were already present before this PR.
Failure scenario: A maintainer relying on the PR description to review the keyword change believes attachments was removed from the published npm package's keywords, but it is still shipped, so the LobeHub listing (generated from these keywords post-merge) still advertises attachments while the description claimed otherwise.
Suggested fix
Update the PR description to state that `second-brain` was added to align cli/package.json keywords with the root package.json and GitHub topics, and that `attachments` was retained.…-crosslink # Conflicts: # README.md
1 participant
Cross-links the new companion project and aligns discovery metadata:
EXCLUDED_H2; regeneratedDOCKERHUB.mdis byte-identical (companion sections don't ship to Docker Hub).attachments→pkm+personal-knowledge-management(keptpdf), matching the GitHub topics update made earlier tonight.Post-merge step (maintainer):
npm run publish:lobehub— the LobeHub listing's tags are generated from package.json keywords.🤖 Generated with Claude Code