Verified:GitHub

verification-before-completion

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

2|Updated Aug 15, 2025

Search Tags:#code quality #testing #commit #verification #evidence #regression testing #build validation

One-click install

npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill verification-before-completion-grupo-6-ads-b

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Grupo-6-ADS-B/FittNutri/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill verification-before-completion-grupo-6-ads-b

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 blocks any completion claim until fresh command output proves it. ## Core Features & Use Cases - Evidence-First Gate: Requires identifying, running, and reading the full output of a verification command before any success claim, commit, or PR. - Claim-to-Command Mapping: Provides a table mapping common claims (tests pass, build succeeds, bug fixed) to the exact evidence required. - Rationalization Detection: Lists red-flag phrases like "should work" or "probably fixed" and counters common excuses for skipping verification. - 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. ## Quick Start Before claiming any task is complete, 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 code changes before committing?▼

Identify the command that proves your claim, such as the test suite or build command, run it fresh, and read the full output including exit code and failure count. Only state the claim after the output confirms it.

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", or linter results do not count as verification.

Does a passing linter mean the build succeeds?▼

No, a linter does not check compilation. You must run the actual build command and confirm it exits with code 0 before claiming the build succeeds.

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.

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 actually exist before reporting the task as complete.