メニュー
Gate skill: run before claiming any work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a major project step has been completed and needs review against the original plan and coding standards. Provides the Senior Code Reviewer persona for structured 6-phase review: plan alignment, code quality, architecture, documentation, issue categorization, and communication.
Use when you need to trigger brainstorm, write-plan, or execute-plan workflows via short command shortcuts. These are thin dispatchers that invoke the corresponding sp- skills.
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Apply TDD cycle: baseline test first, write skill second, refactor to close loopholes.
Use when completing tasks, implementing major features, or before merging. Dispatches a code-reviewer session to catch issues before they cascade. Review early, review often.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Decision framework for when and how to dispatch parallel sub-agent sessions for faster resolution.
Use when implementation is complete and all tests pass, to decide how to integrate the work. Guides branch completion by presenting 4 structured options: merge locally, push and create a PR, keep as-is, or discard.
| name | sp-verification-before-completion |
| description | Gate skill: run before claiming any work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always. |
| tags | ["verification","quality","coding","gate","completeness"] |
| version | 1.0.0 |
| risk | safe |
| triggers | ["verification before completion","verify before claiming done","check before completing","confirm work is complete","run verification","about to claim complete","tests should pass","looks done"] |
| requirements | {"cli":[],"env":[]} |
| upstream_ref | skills/verification-before-completion/SKILL.md |
| author | AlphaComposite |
| license | MIT |
| dependencies | [] |
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
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 or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifying
| Claim | Requires | Not Sufficient |
|---|---|---|
| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
| Regression test works | Red-green cycle verified | Test passes once |
| Agent completed | VCS diff shows changes | Agent reports "success" |
| Requirements met | Line-by-line checklist | Tests passing |
| Excuse | Reality |
|---|---|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ compiler |
| "Agent said success" | Verify independently |
| "I'm tired" | Exhaustion ≠ excuse |
| "Partial check is enough" | Partial proves nothing |
| "Different words so rule doesn't apply" | Spirit over letter |
Tests:
✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"
Regression tests (TDD Red-Green):
✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)
Build:
✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)
Requirements:
✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"
Agent delegation:
✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent report
Core consequences of skipping verification:
ALWAYS before:
Rule applies to:
No shortcuts for verification.
Run the command. Read the output. THEN claim the result.
This is non-negotiable.