菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | clean-cache |
| description | 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". |
Clean up Swift .build/ directories, .DS_Store files, and other accumulated artifacts from Buddy Evolver worktrees.
Run a dry-run first to show the user what will be removed:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/cache-clean.sh" --dry-run --verbose
Show the output to the user. Explain:
.build/ directories are build cache (~33MB each) that rebuild in ~5 seconds on next use.DS_Store files are macOS Finder metadata with no impact.build/ is preserved by default (mention --all if they want total cleanup)Ask the user if they want to proceed with cleanup. If they want to also clean the current worktree's build cache, add --all.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/cache-clean.sh" --verbose
Or with --all if the user requested full cleanup:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/cache-clean.sh" --verbose --all
Show the user:
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 "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".
Use when transitioning from Plan Mode to code execution after a plan has been approved. Prints model/effort recommendations per component and summarizes the approved plan. Use when the user says "execute session", "start building", "plan approved", "begin implementation", or "let's code".