skills.rest
NT-boop-star
NT-boop-starCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforces running verification commands and reading output before claiming work is complete.

Updated Apr 7, 2026
Search Tags:#code quality#testing#tdd#verification#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/NT-boop-star/BRMV-tract --skill verification-before-completion-nt-boop-star
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/NT-boop-star/BRMV-tract/tree/main/antigravity/skills/verification-before-completion
Command: npx skills add https://github.com/NT-boop-star/BRMV-tract --skill verification-before-completion-nt-boop-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is complete, tests pass, or bugs are fixed without actually running verification commands, leading to broken builds, shipped defects, and lost trust. This Skill enforces an evidence-first discipline so no success claim is made without fresh command output. ## Core Features & Use Cases - Verification Gate: A mandatory five-step gate (identify command, run it, read output, verify result, then claim) applied before any completion statement. - Failure Pattern Tables: Concrete mappings of common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Red-flag phrases and excuse counters that stop shortcuts like "should work", "linter passed", or trusting agent success reports. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, verify the regression test fails without the fix, and only then state the fix is verified. ## Quick Start Before claiming any task is done, run the full verification command, read the complete output and exit code, and only then state the result with that evidence.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify work is complete before committing code?▼

Identify the command that proves your claim, run it fresh and in full, read the entire output including exit code, and confirm it matches your claim. Only then state the result, citing the evidence such as test counts or exit status.

What counts as evidence that tests pass?▼

Only the output of a freshly run test command showing zero failures counts as evidence. Previous runs, partial checks, linter results, or assumptions like "should pass" do not qualify as verification.

How do I verify a regression test actually works?▼

Use the red-green cycle: write the test, run it to confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that never fails proves nothing.

Can I trust a linter passing as proof the build works?▼

No. A linter checks style and static issues but does not verify compilation. You must run the actual build command and confirm it exits with code 0 before claiming the build succeeds.

Should I trust an agent's report that a task succeeded?▼

No. Agent success reports are not evidence. Independently verify by checking the version control diff, confirming the expected changes exist, and running relevant verification commands yourself.

Related Skills

Explore More Software Engineering Skills→
Rawgrowth-ConsultingRawgrowth-Consulting

test-driven-development

Enforce a test-driven development workflow with failing tests before production code.

Official
Intermediate
basicmachines-cobasicmachines-co
4.0k

pr-create

Creates or updates Basic Memory pull requests and runs the Codex review loop.

Official
Intermediate
kim-emkim-em
112

proof-review-checklist

Automate Lean proof review with structured checklists and cleanup commands.

Community
Intermediate
amoai-techamoai-tech
1

lean-dev-flow

Guides lean implementation loops with tiered test selection and worktree management for Linear tasks.

Community
Intermediate