メニュー
Use when about to claim work is complete, fixed, or passing — requires running actual verification commands and confirming output before making any success claims
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | verification-before-completion |
| description | Use when about to claim work is complete, fixed, or passing — requires running actual verification commands and confirming output before making any success claims |
Adapted from superpowers:verification-before-completion
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim it passes.
Before claiming ANY status:
| Thought | Reality |
|---|---|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence ≠ evidence |
| "No compiler errors" | Compilation ≠ runtime correctness |
| "Just this once" | No exceptions |
| "The code looks correct" | Reading ≠ running |
| "Great, that's done!" | Did you actually verify? |
Read and update project memory files at start/end of every session. Memory lives in .agents/memory/ and syncs across machines via git.
MANDATORY — STOP and activate BEFORE writing ANY code for new features, significant changes, or multi-file modifications. You MUST ask clarifying questions, explore alternatives, and get explicit design approval first. Do NOT skip this step. Do NOT start coding without approval.
MANDATORY — activate BEFORE pushing to main/master. You MUST analyze the git diff, draft a CHANGELOG.md entry, and get user approval before pushing. No push to main/master is complete without a CHANGELOG update.
Code review expert for Unity C# projects — focuses on performance, serialization, lifecycle correctness, and maintainability.
Use when debugging any issue, fixing a bug, investigating unexpected behavior, or when something isn't working as expected — enforces 4-phase root cause process instead of guessing
Use when planning implementation of a feature, refactoring, or multi-step change — creates bite-sized tasks with exact file paths, code, and verification steps