skills.rest
AliJ021
AliJ021COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

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

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

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. ## Core Features & Use Cases - Evidence-First Gate: Requires identifying, running, and reading the full output of a verification command before any completion claim. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what is not sufficient. - Rationalization Prevention: Lists common excuses like "should work now" or "linter passed" 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, and only then state the fix is verified with the evidence attached. ## Quick Start Before claiming any task is complete, 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 tests pass before committing code?▼

Run the full test command fresh in your current session and read the complete output, confirming zero failures and a successful exit code. Only then claim tests pass, citing the actual output as evidence rather than relying on previous runs.

What counts as sufficient evidence that a bug is fixed?▼

A bug fix is verified by running a test that reproduces the original symptom and confirming it now passes. Changing the code or assuming the fix works is not sufficient evidence without executing the verification.

Does a passing linter mean the build succeeds?▼

No, a linter passing does not prove compilation or build success. Linters check style and syntax patterns but do not verify that the code compiles or bundles correctly, so you must run the actual build command and confirm exit code 0.

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 never fails proves nothing.

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 claimed changes exist and run relevant verification commands yourself before reporting the actual state.

Related Skills

Explore More Software Engineering Skills→
vultisigvultisig
40

build-check

Run SwiftLint and Xcode build checks on iOS projects.

Official
Intermediate
greencmgreencm
1

land-and-deploy

Merge pull requests, run CI tests, and deploy to production with canary checks.

Community
Advanced
ehartyeehartye

test-driven-development

Guide developers through the Red-Green-Refactor cycle with failing tests first.

Community
Advanced
tody-agenttody-agent
48

cm-quality-gate

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

Community
Advanced