skills.rest
gyc-12
gyc-12COMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

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

Updated Jun 9, 2026
Search Tags:#code quality#testing#verification#evidence#regression testing#build validation#completion claims
One-click install
npx skills add https://github.com/gyc-12/Archipelago --skill verification-before-completion-gyc-12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/gyc-12/Archipelago/tree/main/modules/collaboration-runtime/src-tauri/experts/skills/verification-before-completion
Command: npx skills add https://github.com/gyc-12/Archipelago --skill verification-before-completion-gyc-12

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 lost 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) that must be completed before any completion statement. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed, agent completed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Lists red-flag phrases and excuses ("should work", "linter passed", "agent said success") and counters each with the required verification action. - Use Case: Before committing a bug fix, the agent runs the test suite, confirms zero failures in the output, verifies the regression test fails without the fix, and only then reports completion with the evidence attached. ## Quick Start Ask the agent to verify the fix by running the full test suite and only claim completion after confirming the output shows zero failures.

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 together with that evidence. Skipping any step means the claim is unverified.

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

Use a 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.

Does a passing linter mean the build succeeds?▼

No. A linter checks style and static issues but does not compile the code. Build success requires running the actual build command and confirming it exits with code 0.

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.

When should verification be run during a coding task?▼

Run verification before any success claim, expression of satisfaction, commit, pull request, task handoff, or delegation. This applies to exact phrases, paraphrases, and any wording implying completion.

Related Skills

Explore More Software Engineering Skills→
rizqinrrrizqinrr
665

test-driven-development

Implements code changes using the red-green-refactor test-driven development loop.

Community
Intermediate
All-The-VibesAll-The-Vibes
50

land

Commit changes, push to the remote, and open a pull request for handoff.

Official
Advanced
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
kiprotichgidiikiprotichgidii

cicd-automation-workflow-automate

Designs CI/CD pipelines and GitHub Actions workflows for automated build, test, and deployment processes.

Community
Advanced