skills.rest
flowing-abyss
flowing-abyssCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

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

10|1|Updated Jul 29, 2026
Search Tags:#code quality#testing#verification#evidence#regression testing#build validation#completion claims
One-click install
npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill verification-before-completion-flowing-abyss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/flowing-abyss/obsidian-local-fonts/tree/main/.ai/skills/verification-before-completion
Command: npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill verification-before-completion-flowing-abyss

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-first discipline so no completion claim is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Defines a five-step gate (identify, run, read, verify, claim) that must be completed before any success statement. - Failure Pattern Catalog: Maps common claims like "tests pass" or "build succeeds" to the exact evidence required, and lists rationalizations to reject. - 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 with the evidence attached. ## Quick Start Before you claim the task is done, run the full verification command, read its output, and report the result with 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, run it fresh and in full, read the entire output including exit code and failure counts, then state the claim only with that evidence attached. Skipping any step counts as an unverified claim.

What counts as evidence that tests pass?▼

Only the output of a freshly run test command showing zero failures counts as evidence. Previous runs, partial checks, linter results, or assumptions like "should pass" are explicitly not sufficient.

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 version control diff and confirming the actual changes match the claimed work before reporting completion.

Does a passing linter mean the build succeeds?▼

No. A linter does not check compilation, so a clean lint run is not evidence of a successful build. You must run the build command and confirm exit code 0 before claiming the build passes.

Related Skills

Explore More Software Engineering Skills→
arbazkhan971arbazkhan971
26

setup

Detect a repository's stack and validate commands to generate a .godmode/config.yaml.

Community
Advanced
BlackRoad-OS-IncBlackRoad-OS-Inc
1

verification-before-completion

Runs verification commands and reports their outputs before declaring completion.

Official
Intermediate
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
jayhjenkinsjayhjenkins

test-driven-development

Enforce red-green-refactor cycles with tests guiding code implementation.

Community
Basic