skills.rest
eminboydak
eminboydakCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

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

Updated Sep 3, 2024
Search Tags:#code quality#testing#verification#evidence#regression testing#ci#completion claims
One-click install
npx skills add https://github.com/eminboydak/duckTerm --skill verification-before-completion-eminboydak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/eminboydak/duckTerm/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/eminboydak/duckTerm --skill verification-before-completion-eminboydak

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. 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 the proving command before any success 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 flags and excuses ("should work", "linter passed", "agent said success") and counters each with the required verification step. - 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 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 work is complete before committing code?▼

Identify the command that proves your claim, run it fresh and completely, read the full output including exit code, and only then state the 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.

Is a passing linter enough to claim 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.

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 completion.

When should verification before completion be applied?▼

Apply it before any success claim, expression of satisfaction, commit, pull request, task handoff, or delegation. The rule covers exact phrases, paraphrases, and any wording implying completion or correctness.

Related Skills

Explore More Software Engineering Skills→
thiansitthiansit

test-driven-development

Enforce test-first development with failing tests, minimal implementation, and refactoring.

Community
Intermediate
basicmachines-cobasicmachines-co
4.0k

pr-create

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

Official
Intermediate
HKUST-QUANT-SOCIETYHKUST-QUANT-SOCIETY

compose:verify

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

Official
Basic
tody-agenttody-agent
48

cm-quality-gate

Enforce test gates and evidence-based verification before deployment in CI/CD workflows.

Community
Advanced