skills.rest
rinbarpen
rinbarpenCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

Updated Jan 12, 2025
Search Tags:#code quality#testing#commit#validation#verification#evidence#ci
One-click install
npx skills add https://github.com/rinbarpen/NeuroTrain --skill verification-before-completion-rinbarpen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/rinbarpen/NeuroTrain/tree/main/.cursor/commands/verification-before-completion
Command: npx skills add https://github.com/rinbarpen/NeuroTrain --skill verification-before-completion-rinbarpen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents false completion claims by requiring fresh verification evidence—test output, build exit codes, linter results—before any success statement, commit, or PR is made. ## Core Features & Use Cases - Evidence-First Gate: Defines a five-step gate (identify, run, read, verify, claim) that must be completed before any status claim. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what is not sufficient. - Rationalization Blocking: Lists red-flag phrases and excuses ("should work", "just this once") that signal unverified claims. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, then state the result with that evidence instead of assuming the fix worked. ## Quick Start Before claiming any task is done, run the relevant verification command, read its full output, and only then report the result with that 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, run it fresh and in full, read the entire output including exit code, and only then state the result with that evidence. Never commit based on previous runs or assumptions.

What counts as sufficient evidence that tests pass?▼

Only the output of a freshly run test command showing zero failures counts. Previous runs, partial checks, or statements like "should pass" are explicitly not sufficient evidence.

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 exit 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 confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again.

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

No. Agent success reports must be independently verified by checking the VCS diff and confirming the actual changes before reporting the real state of the work.

Related Skills

Explore More Software Engineering Skills→
hardisgroupcomhardisgroupcom
368

test

Build, lint, and test code changes with yarn commands.

Official
Intermediate
caitengweicaitengwei
6

verification-before-completion

Require fresh command execution and evidence before reporting completion status.

Community
Basic
samuelmukotisamuelmukoti

requesting-code-review

Run pre-commit verification pipelines with security scans and quality gates.

Community
Intermediate
sibukixxxsibukixxx

tdd-architect

Guide developers through the Red-Green-Refactor cycle for test-driven development.

Community
Intermediate