菜单
This skill should be used when the user asks to "buddy reset", "reset buddy", "restore buddy", "revert buddy", "undo buddy changes", or "get my original buddy back".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | buddy-reset |
| description | This skill should be used when the user asks to "buddy reset", "reset buddy", "restore buddy", "revert buddy", "undo buddy changes", or "get my original buddy back". |
Restore the user's original Claude Code Buddy by reverting companion data to the pre-evolution state.
echo "Soul backup exists: $(test -f ~/.claude/backups/.claude.json.pre-customize && echo 'yes' || echo 'no')"
echo "Metadata exists: $(test -f ~/.claude/backups/buddy-patch-meta.json && echo 'yes' || echo 'no')"
If the soul backup does not exist, tell the user there is nothing to restore and exit.
plutil -extract companion json -o - ~/.claude.json 2>/dev/null || echo "{}"
Display the current name and personality so the user knows what they are reverting from.
Ask: "This will restore your original companion data and remove the buddy card. Continue?"
"${CLAUDE_PLUGIN_ROOT}/scripts/run-buddy-patcher.sh" --restore
Tell the user:
Your original buddy has been restored.
Changes take effect on your next Claude Code conversation — no restart needed.
Run /buddy-status to confirm the card is cleared.
To re-evolve at any time, run /buddy-evolve.
This skill should be used when the user asks to "security audit", "check security", "audit buddy", "check backup health", "verify backup", or "security check".
This skill should be used when the user asks to "clean cache", "cache clean", "clear build cache", "free disk space", "clean up", "remove build artifacts", "clean .build", "manage cache", or "show cache size".
This skill should be used when the user asks to "token review", "review tokens", "optimize tokens", "audit context size", "reduce token footprint", "session review", "end of session review", or "check token usage".
Pre-commit pipeline for Buddy Evolver — runs token optimization, full test-all.sh, security review, docs sync, and comment audit. INVOKE IMMEDIATELY when the user says any variant of "session review", "review session", "session end", "end session", "end the session", "ending session", "session over", "session done", "wrap up", "wrapping up", "finish up", "finishing up", "done for now", "close out", "ready to commit", or "before commit" — treat these as direct invocations, not topics for discussion. Do NOT ask whether the timing is right, do NOT argue that a commit already happened (run anyway and report what's still actionable), do NOT defer. If the user actively says "don't run" or "skip", honor that — otherwise invoke now.
This skill should be used when the user asks to "sync docs", "update docs", "sync documentation", "update readme", "update claude md", "docs out of date", "check documentation", or "fix docs".
Use after a PR is merged to GitHub main. Syncs local main, verifies the merged code builds, removes merged worktrees, and stages the current worktree for automatic self-cleanup on /exit. With --release, also bumps version, updates CHANGELOG, tags the commit, pushes to trigger marketplace publish, and verifies the local plugin reloads. Use when the user says "deploy", "session deploy", "pr merged", "post-merge sync", "deploy session", "clean up after merge", or "release new version".