skills.rest
michalo1334
michalo1334COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

Updated May 16, 2026
Search Tags:#code quality#testing#verification#discipline#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill verification-before-completion-michalo1334
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/michalo1334/ScenarioImpactDSL/tree/main/.opencode/skills/verification-before-completion
Command: npx skills add https://github.com/michalo1334/ScenarioImpactDSL --skill verification-before-completion-michalo1334

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 builds, shipped defects, and broken trust. 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 mandatory five-step gate (identify, run, read, verify, claim) before any completion statement. - Claim-to-Evidence Mapping: Specifies what proof each claim requires, such as test output showing zero failures or a build exiting with code 0. - Rationalization Blocking: Lists common excuses and red-flag phrases like "should pass" or "agent said success" and counters each with the required verification action. - Use Case: Before committing a bug fix, the agent runs the full test suite, confirms zero failures in the output, and only then reports the fix as verified. ## Quick Start Before claiming any task is done, ask the agent to run the relevant test or build command and report the actual output as 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 the 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 completion after the output confirms the claim.

What counts as evidence that tests pass?▼

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

Does a passing linter prove the build succeeds?▼

No, a linter passing does not prove compilation succeeds because linters do not check compilation. You must run the actual build command and confirm it exits with 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. A test that only passes once is not verified.

Can I trust an agent's success report without checking?▼

No, agent success reports must be independently verified by inspecting the VCS diff and confirming the actual changes exist. Trusting a report without checking the repository state is a listed common failure.

Related Skills

Explore More Software Engineering Skills→
yuichi176yuichi176

code-change-verification

Install dependencies, build, lint, typecheck, and test code changes.

Community
Intermediate
basicmachines-cobasicmachines-co
4.0k

pr-create

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

Official
Intermediate
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
grasberggrasberg
3

tdd-workflow

Enforce a RED-GREEN-REFACTOR test-first workflow with AAA patterns.

Community
Intermediate