skills.rest
johsquaree
johsquareeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforces running verification commands and checking output before making any completion claims.

Updated Jul 30, 2026
Search Tags:#code quality#testing#debugging#verification#evidence#ci#completion claims
One-click install
npx skills add https://github.com/johsquaree/claude-basic-docs --skill verification-before-completion-johsquaree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/johsquaree/claude-basic-docs/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/johsquaree/claude-basic-docs --skill verification-before-completion-johsquaree

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 false success reports and broken commits. This Skill enforces an evidence-before-claims discipline so every completion statement is backed by fresh command output. ## Core Features & Use Cases - Verification Gate: Requires identifying, running, and reading the full output of a proof command before any success claim is made. - Failure Pattern Detection: Lists common false claims (tests pass, linter clean, build succeeds, bug fixed) and the exact evidence each one requires. - Rationalization Blocking: Counters excuses like "should work", "just this once", or trusting agent success reports without independent checks. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, verify the regression test fails without the fix, and only then report completion with evidence. ## Quick Start Before claiming any task is done, 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 complete output including exit code and failure counts, then state your claim 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 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.

Does a passing linter mean the build succeeds?▼

No. A linter checks style and static issues but does not verify compilation. You must run the actual build command and confirm exit code 0 before claiming the build succeeds.

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

No. Agent success reports must be independently verified by checking the version control diff and confirming the actual changes match the claimed work before reporting completion.

When should verification be skipped for small changes?▼

Never. The rule has no exceptions: partial checks, confidence, fatigue, or "just this once" reasoning all violate the requirement. Every completion claim requires fresh verification evidence.

Related Skills

Explore More Software Engineering Skills→
adschilladschill

tdd-development

Enforces test-first workflow for code changes with focused failing tests and verification.

Community
Intermediate
basicmachines-cobasicmachines-co
4.0k

pr-create

Creates or updates Basic Memory pull requests and runs the Codex review loop.

Official
Intermediate
sunghwanismsunghwanism

verification-engine

Automate build, test, and lint workflows with failure analysis and fix suggestions.

Community
Intermediate
mahg-esmahg-es
3

cicd-quality

Design and enforce CI/CD quality gates for code, tests, security, build, E2E, and performance.

Official
Advanced