skills.rest
thienty1207
thienty1207COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Requires running verification commands and checking output before claiming work is complete.

1|Updated Sep 10, 2026
Search Tags:#code quality#testing#verification#evidence#regression testing#build validation#completion claims
One-click install
npx skills add https://github.com/thienty1207/Hotel_Staff --skill verification-before-completion-thienty1207
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/thienty1207/Hotel_Staff/tree/main/.baron/core/skills/superpowers/verification-before-completion
Command: npx skills add https://github.com/thienty1207/Hotel_Staff --skill verification-before-completion-thienty1207

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 false success reports and broken commits. ## Core Features & Use Cases - Evidence-First Gate: Enforces a strict sequence of identifying the proof command, running it fresh, reading full output, and only then making any completion claim. - 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 counters each with the required verification action. - 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 the evidence attached. ## Quick Start Before claiming any task is complete, run the full verification command, read its output and exit code, and state the result only 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, such as the test suite or build command, run it fresh and completely, then read the full output and exit code. Only state the claim after the output confirms it, citing the evidence.

What counts as evidence that tests pass?▼

Evidence is the actual output of a freshly run test command showing zero failures. Previous runs, assumptions like "should pass", linter results, or partial checks do not count as verification.

How do I verify a regression test actually works?▼

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

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

No, agent success reports must be independently verified. Check the version control diff to confirm the changes exist and run the relevant verification commands yourself before reporting the actual state.

Why is a passing linter not enough to claim a build succeeds?▼

A linter checks style and static issues but does not compile the code. Claiming a build succeeds requires running the actual build command and confirming it exits with code zero.

Related Skills

Explore More Software Engineering Skills→
Sma1lboySma1lboy
136

tdd

Writes failing regression tests before fixing bugs with clear test paths.

Community
Intermediate
All-The-VibesAll-The-Vibes
50

land

Commit changes, push to the remote, and open a pull request for handoff.

Official
Advanced
kid-sidkid-sid
18

end-to-end-testing

Validate complete user workflows across the application stack with browser automation.

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