skills.rest
Yvesdefaria
YvesdefariaCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

Updated Aug 3, 2026
Search Tags:#code quality#testing#debugging#verification#evidence#ci#completion claims
One-click install
npx skills add https://github.com/Yvesdefaria/GymLab --skill verification-before-completion-yvesdefaria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Yvesdefaria/GymLab/tree/main/.opencode/skills/verification-before-completion
Command: npx skills add https://github.com/Yvesdefaria/GymLab --skill verification-before-completion-yvesdefaria

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 - Gate Function Workflow: A five-step process (identify, run, read, verify, claim) that must be completed before any success claim is made. - Failure Pattern Tables: Concrete mappings of claims (tests pass, build succeeds, bug fixed) to the exact evidence required, plus red flags and rationalization countermeasures. - 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, instead of assuming the code change worked. ## Quick Start Ask the agent to verify the fix with fresh test output before claiming the task is complete.

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, run it fresh and in full, read the entire output including exit code and failure counts, then state the claim only with that evidence. Never commit based on previous runs or assumptions.

How to confirm a bug fix actually works?▼

Run a test that reproduces the original symptom and confirm it passes after the fix. For regression tests, follow the red-green cycle: verify the test fails when the fix is reverted, then passes when restored.

Does a passing linter mean the build succeeds?▼

No. A linter does not check compilation, so lint output cannot prove a build succeeds. You must run the actual build command and confirm it exits with code 0 before claiming the build passes.

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 changes exist and work. Trusting a report without evidence violates the evidence-before-claims rule.

When should verification-before-completion not be skipped?▼

It applies always: before commits, pull requests, task completion, delegation, and any wording implying success. Partial checks, confidence, fatigue, or 'just this once' reasoning are explicitly rejected as excuses.

Related Skills

Explore More Software Engineering Skills→
raddueraddue
10

verify

Verify test results, linter status, and build success via command output.

Community
Basic
lucasocostalucasocosta

cy-final-verify

Enforces fresh verification evidence before completion claims, commits, and pull requests.

Community
Intermediate
KirillKlemKirillKlem
1

minimal-validation

Run the smallest credible set of tests for code changes.

Community
Intermediate
jimmymalhanjimmymalhan
1

auto-merge

Merge pull requests automatically after CI checks pass.

Community
Intermediate