🎯

verification-before-completion

🎯Skill

from codingcossack/agent-skills-library

VibeIndex|
What it does

Enforces rigorous verification by requiring concrete evidence and specific command outputs before claiming task completion or success.

πŸ“¦

Part of

codingcossack/agent-skills-library(14 items)

verification-before-completion

Installation

πŸ“‹ No install commands found in docs. Showing default command. Check GitHub for actual instructions.
Quick InstallInstall with npx
npx skills add codingcossack/agent-skills-library --skill verification-before-completion
1Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.

Overview

# Verification Before Completion

> NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Core Protocol

Evidence before claims, always. If you haven't run the verification command in this message, you cannot claim it passes.

```

BEFORE any completion claim:

  1. IDENTIFY: What verification 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?

- NO β†’ State actual status with evidence

- YES β†’ State claim WITH evidence

  1. ONLY THEN: Make the claim

```

Command Selection

When multiple verification options exist (mono-repo, multiple suites):

  • Run the most specific command that covers the changed code
  • When uncertain, run the broadest command (full test suite > single file)
  • Lint β‰  build β‰  test β€” each verifies different claims

Evidence Format

```

βœ… Ran: npm test

Exit: 0

Result: 47 passed, 0 failed

"All tests pass."

❌ "Tests should pass now" (no command output)

```

Verification Requirements by Claim Type

| Claim | Required Evidence | Insufficient |

|-------|-------------------|--------------|

| Tests pass | Test output: 0 failures | Previous run, "should pass" |

| Linter clean | Linter output: 0 errors | Partial check, extrapolation |

| Build succeeds | Build exit code: 0 | Linter passing |

| Bug fixed | Original symptom test passes | Code changed |

| Regression test | Red-green cycle verified | Single green |

| Agent completed | VCS diff shows changes | Agent "success" report |

| Requirements met | Line-by-line checklist | Tests passing |

Red Flags β€” STOP

  • Words: "should", "probably", "seems to"
  • Satisfaction before verification: "Great!", "Perfect!", "Done!"
  • About to commit/push/PR without verification
  • Trusting agent success reports
  • Partial verification
  • ANY wording implying success without verification output

Rationalization Prevention

| Excuse | Response |

|--------|----------|

| "Should work now" | Run the verification |

| "I'm confident" | Confidence β‰  evidence |

| "Just this once" | No exceptions |

| "Linter passed" | Linter β‰  build |

| "Agent said success" | Verify independently |

| "Partial check enough" | Partial proves nothing |

Key Patterns

Tests:

```

βœ… [Run test] β†’ [See: 34/34 pass] β†’ "All tests pass"

❌ "Should pass now"

```

Regression (TDD):

```

βœ… Write β†’ Run (pass) β†’ Revert fix β†’ Run (MUST FAIL) β†’ Restore β†’ Run (pass)

❌ "Wrote regression test" (no red-green)

```

Requirements:

```

βœ… Re-read plan β†’ Checklist each item β†’ Report gaps or completion

❌ "Tests pass, phase complete"

```

Agent delegation:

```

βœ… Agent reports β†’ Check VCS diff β†’ Verify changes β†’ Report actual state

❌ Trust agent report

```

More from this repository10

🎯
brainstorming🎯Skill

Collaboratively explores and refines ideas into validated design specifications through iterative, focused questioning and incremental validation.

🎯
finishing-a-development-branch🎯Skill

Guides developers through safely completing a feature branch by running tests, determining merge target, and offering merge or PR options.

🎯
using-superpowers🎯Skill

I apologize, but I cannot generate a description without seeing the actual content or context of the "using-superpowers" skill from the repository. Could you provide more details about the skill's ...

🎯
test-driven-development🎯Skill

I apologize, but I cannot generate a description without seeing the actual content or context of the "test-driven-development" skill from the repository. Could you provide more details about the sk...

🎯
requesting-code-review🎯Skill

Requests a comprehensive code review from an AI assistant, providing detailed feedback on code quality, potential improvements, and best practices.

🎯
systematic-debugging🎯Skill

Systematically diagnoses and resolves software bugs by methodically analyzing code, tracing errors, and applying targeted debugging techniques.

🎯
receiving-code-review🎯Skill

Systematically evaluates and responds to code review feedback, verifying technical correctness and alignment with project requirements before implementation.

🎯
executing-plans🎯Skill

Systematically executes implementation plans by loading, critically reviewing, executing tasks in batches, and reporting progress for architect feedback.

🎯
writing-skills🎯Skill

Guides skill creation through test-driven development by documenting proven techniques, patterns, and tools for future Claude instances to reference and apply effectively.

🎯
writing-plans🎯Skill

I apologize, but I cannot generate a description without seeing the actual content or context of the "writing-plans" skill from the repository. Could you provide me with more details about what thi...