skills.rest
Viranya2006
Viranya2006COMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

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

Updated Aug 13, 2026
Search Tags:#code quality#testing#verification#evidence#regression testing#build validation#completion claims
One-click install
npx skills add https://github.com/Viranya2006/Lumen --skill verification-before-completion-viranya2006
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Viranya2006/Lumen/tree/main/SKILLS/verification-before-completion
Command: npx skills add https://github.com/Viranya2006/Lumen --skill verification-before-completion-viranya2006

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 false success reports, broken commits, and premature pull requests. ## Core Features & Use Cases - Evidence-First Gate: Requires identifying, running, and reading the full output of a verification command before any completion claim is made. - Claim-to-Evidence Mapping: Defines what proof each claim type requires, such as test output showing zero failures, build exit code 0, or red-green regression cycles. - Rationalization Blocking: Lists common excuses like "should work now" or "linter passed" and explains why each is insufficient evidence. - Use Case: Before committing a bug fix, an agent runs the failing test, confirms it passes, reverts the fix to confirm the test fails, then restores the fix and reports the verified result with evidence. ## Quick Start Before claiming any task is done, run the relevant test or build 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. For tests, confirm zero failures; for builds, confirm exit code 0.

How to verify a regression test actually catches the bug?▼

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 works?▼

No, a linter does not check compilation. Linters catch style and syntax issues but do not verify the code compiles or builds successfully. You must run the actual build command and confirm exit code 0.

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

No, agent success reports require independent verification. Check the version control diff to confirm changes exist, run the relevant verification commands yourself, and report the actual verified state rather than the agent's claim.

When should verification be run during a coding workflow?▼

Run verification before any success claim, expression of satisfaction, commit, pull request, task completion, or handoff to another agent. The rule applies to exact phrases, paraphrases, and any implication of success.

Related Skills

Explore More Software Engineering Skills→
John2143John2143
2

gh-validate

Execute build, test, and lint commands and report pass/fail status.

Community
Advanced
GenEducationGenEducation

ship

Prepare feature branches for release with tests, versioning, and pull requests.

Official
Advanced
Obsidian-OwlObsidian-Owl
9

gate-build

Execute configured build and test commands to verify code integrity.

Official
Intermediate
tody-agenttody-agent
48

cm-quality-gate

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

Community
Advanced