From vault-sync
Review and promote exploratory notes to established status after branch merge
How this skill is triggered — by the user, by Claude, or both
Slash command
/vault-sync:promoteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are guiding the developer through reviewing exploratory notes captured during a feature branch and deciding which to promote to `established` status, edit before promoting, or discard.
You are guiding the developer through reviewing exploratory notes captured during a feature branch and deciding which to promote to established status, edit before promoting, or discard.
If the current git branch is main or master:
Run:
git log --merges --oneline -10
Show the output to the user and ask: "Which recently merged branch would you like to promote notes from? Enter the branch name."
Accept the branch name as input.
If the current git branch is a feature branch:
Use that branch name automatically. Inform the user: "Reviewing exploratory notes from branch: <branch>."
Call vault-query with:
status: "exploratory"branch: <branch-name>If no notes are returned:
Print:
No exploratory notes found for branch <branch>.
If notes exist in the vault under a different branch name, run /vault-cleanup to find them.
Stop here.
If notes are returned but all are already established:
Print:
All notes from branch <branch> have already been promoted. Nothing to do.
Stop here.
Dispatch the promoter agent, passing:
Wait for the agent to return structured recommendations before continuing.
For each note, display the agent's recommendation in this format:
Note: <title>
Recommendation: <Promote as-is | Edit then promote | Discard>
Reason: <agent's reasoning>
What would you like to do?
[P] Promote as-is
[E] Edit & promote
[D] Discard
[S] Skip (decide later)
Accept a single letter response for each note. Process notes one at a time.
If the user chooses [E] Edit & promote:
vault-update-noteFor each note where the user chose Promote or Edit & promote:
Call vault-promote with:
note_id: the note's identifierpromoted_by: the current GitHub username (from vault config)promoted_at: today's date in ISO format (YYYY-MM-DD)For each note where the user chose Discard:
Call vault-discard with:
note_id: the note's identifierreason: "reviewed after merge — not worth keeping"After all decisions are processed, print:
Promotion complete for branch <branch>:
Promoted: N notes
Discarded: N notes
Skipped: N notes
Promoted notes are now available to the whole team in the vault.
Skipped notes remain exploratory — run /promote-to-vault again to revisit them.
npx claudepluginhub mahuebel/lore --plugin vault-syncOrchestrates GitHub issues/PRs/branches as knowledge graph for traceability in planning, brainstorming, designs, architectural decisions, session resumption. /shiplog.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.