skills.rest
AarushiShah
AarushiShahCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

Updated Mar 24, 2026
Search Tags:#code quality#testing#verification#test-driven development#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill verification-before-completion-aarushishah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/AarushiShah/coding-agents-databricks-apps/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill verification-before-completion-aarushishah

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 code, lost trust, and wasted rework. 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 common excuses like "should work now" or "linter passed" and explains why each is insufficient. - 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 full verification command, read the complete output and exit code, and only then state the result with the 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 code changes before committing?▼

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 the exit code. Only state the change is complete after the output confirms zero failures.

What counts as evidence that tests pass?▼

Evidence is the actual output of the test command showing zero failures from a fresh run in the current session. Previous runs, partial checks, or assumptions that tests should pass do not qualify as verification.

Does a passing linter mean the build succeeds?▼

No, a linter only checks style and static issues, not compilation. Build success requires running the actual build command and confirming it exits with code zero.

How do I verify a regression test actually works?▼

Use the red-green cycle: write the test, 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.

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

No, agent success reports must be independently verified by checking the version control diff and confirming the actual changes exist. Trusting the report without inspection is a listed failure mode.

Related Skills

Explore More Software Engineering Skills→
Rawgrowth-ConsultingRawgrowth-Consulting

test-driven-development

Enforce a test-driven development workflow with failing tests before production code.

Official
Intermediate
SeanChenRSeanChenR

verification-before-completion

Require fresh verification commands and output inspection before completion claims.

Community
Intermediate
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
buchananwillbuchananwill
2

commit-discipline

Commit work units with descriptive messages and auto-push to a bare repository.

Community
Basic