From obsidian-knowledge
Merge an approved harness branch into main, bump patch version, push to origin. Callable manually for hand-edited changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-knowledge:deploy-harnessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Single-purpose skill: ship a branch.
Single-purpose skill: ship a branch.
<branch> — branch name to merge (typically improve/<slug>)Verify cwd is plugin repo:
git remote get-url origin
Confirm origin is the obsidian-knowledge repo.
Verify branch exists locally:
git branch --list <branch>
Checkout main and pull latest:
git checkout main && git pull origin main
Merge no-ff:
git merge --no-ff <branch>
If merge conflicts: STOP. Surface to user. Do not attempt resolution autonomously.
Bump patch version in .claude-plugin/plugin.json:
Stage version bump:
git add .claude-plugin/plugin.json
git commit -m "chore(harness): release v<X.Y.Z+1>"
Push to origin:
git push origin main
Delete the merged branch locally:
git branch -d <branch>
Report to caller:
git rev-parse HEAD<X.Y.Z+1>)<branch> was deleted locallygit status shows uncommitted changes — abort with message.npx claudepluginhub crypdick/obsidian-knowledgeCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.