skills.rest
ksolomon
ksolomonCOMMUNITY
Explore all skills by this author →
Website𝕏@KeithInWpgGitHub

verification-before-completion

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

1|Updated Jul 6, 2015
Search Tags:#code quality#testing#verification#test-driven development#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill verification-before-completion-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/cache/claude-plugins-official/superpowers/6.1.1/skills/verification-before-completion
Command: npx skills add https://github.com/ksolomon/dotfiles --skill verification-before-completion-ksolomon

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 broken code, lost trust, and wasted rework. This Skill enforces an evidence-before-claims discipline so no success statement is made without fresh command output. ## Core Features & Use Cases - Verification Gate Function: A five-step process (identify, run, read, verify, claim) that must be completed before any completion claim. - Failure Pattern Tables: Concrete mappings of common claims (tests pass, build succeeds, bug fixed) to the exact evidence required, plus rationalization and red-flag checklists. - Use Case: Before committing a bug fix, the agent runs the full test suite, confirms zero failures in the output, and only then reports "All tests pass" with the evidence attached. ## Quick Start Before claiming the fix is complete, run the full test suite and show me the output confirming 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 your claim, run it fresh and in full, read the complete output including exit code, and only then state the result with that evidence. Skipping any step means the claim is unverified.

What evidence is required before claiming tests pass?▼

Claiming tests pass requires output from an actual test command run showing zero failures. Previous runs, partial checks, or assumptions like "should pass" are not sufficient evidence.

How do I verify a regression test actually works?▼

Use a 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 only passes once is not verified.

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

No, a linter passing does not prove compilation succeeds. Linters check style and syntax patterns, not compilation, so you must run the actual build command and confirm exit code 0.

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

No, agent success reports must be verified independently. Check the version control diff to confirm the changes actually exist and match the claimed work before reporting completion.

Related Skills

Explore More Software Engineering Skills→
rizqinrrrizqinrr
665

test-driven-development

Implements code changes using the red-green-refactor test-driven development loop.

Community
Intermediate
caitengweicaitengwei
6

verification-before-completion

Require fresh command execution and evidence before reporting completion status.

Community
Basic
kim-emkim-em
112

proof-review-checklist

Automate Lean proof review with structured checklists and cleanup commands.

Community
Intermediate
hadpadrahulhadpadrahul

gsd-audit-fix

Automate code quality issue detection, classification, and test-verified fixes.

Community
Advanced