菜单
Report whether a newer kit release exists on GitHub — compares the installed plugin version against the latest GitHub Release and prints either "up to date" or "vX.Y.Z available — run /update-kit". Use for "/check-updates", "check for updates", "is the kit up to date?".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run one task through the plan→build→review pipeline — a Step-0.5 classify-task call routes the planner/implementer/reviewer models to the task's complexity tier, then the plan is written (planner subagent or inline), the implementer builds it in an isolated worktree, the my-review agent reviews the diff, and findings route by severity (low→issues, medium→triaged fix-list, high→collective replan, critical→own cycle). For single tasks not worth slicing into an issue graph. Use for "/pipeline <issue#|task>", "pipeline this".
Deep, security-weighted review of your changes or a PR — routes the reviewer model to the change's complexity (opus by default; fable for a complex diff, on ask), then spawns the my-review agent (xhigh reasoning) on that model. Read-only, report-only. Use for "/my-review", "/my-review <PR#>".
Classify one task or issue into a complexity tier — trivial, standard, or complex — and emit that tier plus a rationale; consumers resolve the tier's {model, effort} roster via the plugin's resolve-tier.sh. Grounds the call by fanning out 1–3 Explore subagents over the touched codebase areas, then asks you to confirm or override. Use for "/classify-task <issue#|brief>", "classify this task".
Run N rounds of the autonomous issue-solving loop — pick the ready set (blockers closed, skip hitl), fan out parallel implementers in isolated git worktrees, hand the completed branches to a merger that merges in dependency order and resolves conflicts under the done-check, close finished issues, then a reviewer files blocking follow-ups. Use for "/orchestrate", "run the loop", "build the ready issues".
Check whether the plan(s)/PRD(s)/issue-slice(s) under discussion still match the decisions made in this session — a sonnet subagent reads the current session log, later decisions win, and reports drift read-only. Use for "/verify-plan", "does my plan still match what we decided?".
Capture the just-approved plan after exiting plan mode and hand it to a fresh session — write the plan to a file plus the resume pointer the workflow plugin reads, then tell me to /clear and send `go` to execute it. Use for "/handoff-plan", "hand off this plan".
| name | check-updates |
| description | Report whether a newer kit release exists on GitHub — compares the installed plugin version against the latest GitHub Release and prints either "up to date" or "vX.Y.Z available — run /update-kit". Use for "/check-updates", "check for updates", "is the kit up to date?". |
| argument-hint | |
| model | inherit |
| allowed-tools | Bash |
Check whether a newer kit release is available. No arguments needed.
Locate the backing script — it lives at
${CLAUDE_PLUGIN_ROOT}/scripts/check-update.sh.
Run it with Bash:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-update.sh"
The script reads the installed version from
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json, queries the GitHub
Releases API, and compares the two by numeric semver ordering
(major.minor.patch). It prints one of:
kit is up to date (vX.Y.Z) — installed version is equal to or newer than
the latest release (a local/dev checkout that is ahead is never asked to
downgrade).vX.Y.Z available — run /update-kit to upgrade — the latest release is
strictly newer than the installed version.On any network or API failure the script exits 0 with no output (fail-open).
Report the result. Relay the script output to the user. If the script prints nothing (network failure or no version info available), tell the user that the update check could not be completed and to try again later.