skills.rest
viniciuscs84
viniciuscs84COMMUNITY
Explore all skills by this author →
Website𝕏@viniciuscs84GitHub

verification-before-completion

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

Updated May 22, 2026
Search Tags:#code quality#testing#tdd#verification#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill verification-before-completion-viniciuscs84
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/viniciuscs84/sdd-toolkit/tree/main/skills/verification-before-completion%20copy
Command: npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill verification-before-completion-viniciuscs84

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: A mandatory five-step gate (identify, run, read, verify, claim) that must be completed before any completion statement. - Failure Pattern Catalog: Tables mapping common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Explicit counterarguments for excuses like "should work", "linter passed", or "agent said success". - Use Case: Before committing a bug fix, the agent runs the full test suite, confirms zero failures in the output, and only then reports the fix as verified with the evidence attached. ## Quick Start Ask the agent to verify the fix by running the full test suite and only claim completion after confirming the output shows zero failures.

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 the claim, run it fresh and in full, read the entire output including exit code, and confirm it matches the claim. Only then state the result, citing the evidence such as "34/34 tests pass".

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 run again to confirm it fails, then restore the fix and confirm it passes. A test that never fails proves nothing.

Does a passing linter mean the build succeeds?▼

No. A linter checks style and static issues but does not compile the code. Build success requires running the actual build command and confirming exit code 0.

Can I trust an agent's success report without checking?▼

No. Agent success reports must be independently verified by inspecting the VCS diff and confirming the actual changes exist. Trusting the report alone is listed as a common failure mode.

When should verification be skipped to save time?▼

Never. The skill states there are no exceptions: partial checks, confidence, fatigue, or "just this once" reasoning all count as violations. Skipping verification is treated as dishonesty, not efficiency.

Related Skills

Explore More Software Engineering Skills→
ruskicoderruskicoder
3

code-quality-testing

Write runnable code and execute unit tests, integration tests, and linter passes.

Community
Intermediate
SeanChenRSeanChenR

verification-before-completion

Require fresh verification commands and output inspection before completion claims.

Community
Intermediate
nateanatea

shift-left-testing

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

Community
Advanced
sumeetonline90sumeetonline90

plankton-code-quality

Run formatters and linters automatically on every file edit via Claude Code hooks.

Community
Advanced