菜单
Recover from failed tool calls, bad routing, missing context, or failed verification. Diagnose, avoid retry loops, choose an alternate path, escalate only when truly blocked. Use when something failed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Review code changes for correctness, error handling, scope creep, and style. Use when the goal mentions reviewing a PR, diff, or file.
Walk through a stack trace or error log to find the root cause. Use when the goal mentions debugging, investigating an error, or tracking down a bug.
Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes.
Outline unit tests for a function or module before writing them. Use when the goal mentions writing tests, test plan, or test coverage.
Keep effort proportional to risk — prefer the cheapest sufficient workflow, escalate only on evidence, refuse over-analysis on simple tasks. Use when choosing depth, level, or workflow shape.
Map required capabilities to persona roles and available skills. Detect missing skill coverage and decide whether to acquire a skill, request one, or proceed generically. Use when scoping a workflow.
| name | recovery-replan |
| description | Recover from failed tool calls, bad routing, missing context, or failed verification. Diagnose, avoid retry loops, choose an alternate path, escalate only when truly blocked. Use when something failed. |
When something fails, the temptation is to retry harder. Most retries fail the same way. Recovery starts with diagnosis, not repetition.
A short recovery note: what failed · class · move taken · result · escalation if any. So the next run can learn from it.
