skills.rest
ryuya-matsunawa
ryuya-matsunawaCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

Updated Sep 16, 2022
Search Tags:#code quality#testing#tdd#verification#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/ryuya-matsunawa/dotfiles --skill verification-before-completion-ryuya-matsunawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ryuya-matsunawa/dotfiles/tree/main/agents/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/ryuya-matsunawa/dotfiles --skill verification-before-completion-ryuya-matsunawa

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 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: Defines a five-step gate (identify, run, read, verify, claim) that must be completed before any completion statement. - 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: Lists red-flag phrases and excuses like "should work" or "linter passed" that signal unverified claims. - Use Case: Before committing a bug fix, the agent runs the test suite, confirms zero failures in the output, and only then reports the fix as verified with the 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 work is complete before committing code?▼

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

What counts as evidence that tests pass?▼

Evidence is the actual output of a freshly run test command showing zero failures. Previous runs, assumptions like "should pass", or partial checks do not qualify as verification.

Does a passing linter mean the build succeeds?▼

No, a linter passing does not prove compilation or build success. You must run the actual build command and confirm it exits with code 0 before claiming the build passes.

How do I verify a regression test actually works?▼

Use the red-green cycle: write the test, run it to see it pass 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 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.

Related Skills

Explore More Software Engineering Skills→
mattniedelmanmattniedelman

test-driven-development

Guide teams through Red-Green-Refactor cycles for features, bug fixes, and refactors.

Community
Basic
caitengweicaitengwei
6

verification-before-completion

Require fresh command execution and evidence before reporting completion status.

Community
Basic
shygolyshygoly

springboot-verification

Automate Spring Boot verification with builds, static analysis, tests, and security scans.

Community
Advanced
openaiopenai
5.3k

test-driven-development

Enforces test-first development using the red-green-refactor cycle for features and bug fixes.

Official
Intermediate