fix
Use when verify failed, same error twice, or something is broken. Diagnose before retry; not for first green build.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when verify failed, same error twice, or something is broken. Diagnose before retry; not for first green build.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a plan or concrete tasks exist and user said build/go/implement. Not to invent scope or claim done without verify.
Use when goal/spec is clear and you need ordered tasks before writing code. Not while still clarifying.
Use when about to claim done/works/fixed, or user asks test/check/prove. Run evidence; not for pure planning chat.
Use when another installed plugin/skill may do the job better, or to route specialists. ACC stays workflow owner.
Use when user wants an explicit recorded decision or blocker saved to artifacts. Not silent monitoring.
Use when request is too vague to plan or build. Not when goal and constraints are already clear.
| name | fix |
| description | Use when verify failed, same error twice, or something is broken. Diagnose before retry; not for first green build. |
Reply rule:
Use $fix when verification keeps failing or the current route needs controlled recovery.
.codex/anyone-can-code/state/turn-ledger.jsonl.codex/anyone-can-code/artifacts/VERIFICATION.md.codex/anyone-can-code/artifacts/resume-note.mdNext: $execute for the repair, then $verify again.
When this skill's job is finished: