skills.rest
stefanfaur
stefanfaurCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

1|Updated Feb 10, 2026
Search Tags:#code quality#testing#debugging#verification#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill verification-before-completion-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/verification-before-completion
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill verification-before-completion-stefanfaur

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 the verification commands, leading to broken code, lost trust, and wasted rework cycles. ## Core Features & Use Cases - Evidence-First Gate: Requires identifying, running, and reading the full output of a verification command before any success claim is made. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Counters excuses like "should work", "linter passed", or "agent said success" with mandatory fresh verification. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, and only then state the fix is verified with that evidence attached. ## Quick Start Before claiming any task is done, run the relevant test or build command and report the actual output as 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 code changes before committing?▼

Identify the command that proves your claim, such as the test suite or build command, run it fresh and completely, then read the full output and exit code. Only state the change works after the output confirms it.

What counts as evidence that tests pass?▼

Evidence is the actual output of a freshly run test command showing zero failures. Previous runs, partial subsets, linter results, or confidence that it should pass do not count 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.

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

No, agent success reports must be independently verified. Check the version control diff to confirm actual changes were made and run the relevant verification commands yourself before reporting completion.

Why is linter output not enough to claim a build succeeds?▼

Linters check style and static issues but do not compile or build the code. A build claim requires running the actual build command and confirming it exits with code zero.

Related Skills

Explore More Software Engineering Skills→
g2i-aig2i-ai
51

tdd

Guide test-driven development with red-green-refactor cycles and quality checks.

Official
Intermediate
mattsp1290mattsp1290

ship

Coordinate review, fix, verify, commit, push, and pull request processes.

Community
Advanced
nateanatea

shift-left-testing

Validate requirements and generate tests earlier in CI/CD pipelines.

Community
Advanced
cncorpcncorp

test-runner

Run ruff, lint, and parallel mocked, e2e-live, and smoke tests.

Official
Intermediate