skills.rest
Fidasek009
Fidasek009COMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforces running verification commands before claiming work is complete or passing.

1|Updated Dec 30, 2025
Search Tags:#code quality#testing#debugging#verification#ci-cd#evidence-based#completion claims
One-click install
npx skills add https://github.com/Fidasek009/agents --skill verification-before-completion-fidasek009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Fidasek009/agents/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/Fidasek009/agents --skill verification-before-completion-fidasek009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is done, tests pass, or bugs are fixed without actually running the verification commands, leading to false success reports and broken commits. This Skill enforces an evidence-before-claims discipline so no completion statement is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Requires identifying, running, and reading the full output of the proving command before any success claim. - Failure Pattern Detection: Flags red-flag language like "should pass", "probably works", or premature satisfaction expressions. - Rationalization Prevention: Counters common excuses such as trusting agent reports, partial checks, or "just this once" reasoning. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, and only then state that the fix passes with the evidence attached. ## Quick Start Before claiming any task is complete, run the relevant verification command and report the actual output alongside your claim.

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 only then state the result with that evidence. Never commit based on previous runs or assumptions.

How to verify a regression test actually works?▼

Use the red-green cycle: write the test, run it to confirm it passes, 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 an AI agent's success report?▼

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

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

Linters check style and syntax but do not compile code. A build claim requires running the actual build command and confirming exit code 0, since compilation errors are invisible to linting tools.

When should verification-before-completion not be skipped?▼

It should never be skipped, including when tired, confident, or under time pressure. The rule applies to any wording implying success, including paraphrases, satisfaction expressions, and partial verification results.

Related Skills

Explore More Software Engineering Skills→
Sma1lboySma1lboy
136

tdd

Writes failing regression tests before fixing bugs with clear test paths.

Community
Intermediate
SeanChenRSeanChenR

verification-before-completion

Require fresh verification commands and output inspection before completion claims.

Community
Intermediate
coco-decoco-de

code-review

Coordinates manual and automated checks for systematic code review across eight quality dimensions.

Official
Intermediate
tody-agenttody-agent
48

cm-quality-gate

Enforce test gates and evidence-based verification before deployment in CI/CD workflows.

Community
Advanced