skills.rest
AlabamaMike
AlabamaMikeCOMMUNITY
Explore all skills by this author →
Website𝕏@alabamamikeGitHub

verification-before-completion

Run verification commands and confirm fresh outputs before declaring completion.

Updated Oct 28, 2025
Search Tags:#workflow#testing#quality assurance#best practices#verification#completion#evidence#trust
One-click install
npx skills add https://github.com/AlabamaMike/copilot-agents --skill verification-before-completion-alabamamike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/AlabamaMike/copilot-agents/tree/main/.codex/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/AlabamaMike/copilot-agents --skill verification-before-completion-alabamamike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete or fixed without fresh, explicit verification leads to false confidence, broken trust, and wasted time on rework. This skill enforces a strict protocol: always run verification commands and confirm their output before making any success claims. It ensures that every assertion is backed by undeniable evidence, preventing premature completion and ensuring quality.

Core Features & Use Cases

  • Mandatory Verification Gate: Requires running and confirming output of verification commands before any completion claims.
  • Evidence-Based Assertions: Ensures all claims (tests pass, build succeeds, bug fixed) are backed by fresh, complete evidence.
  • Rationalization Prevention: Explicitly counters common excuses for skipping verification, like "should work now" or "I'm confident."
  • Use Case: Before committing your code or creating a Pull Request, use this skill to run all necessary tests and build commands, verifying their output and ensuring your work is truly complete and correct.

Quick Start

Use the verification-before-completion skill to confirm all tests pass for the 'user-registration' module.

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 my code changes are actually working before committing?▼

Verification-before-completion requires you to run your verification commands—tests, builds, or checks—in full and confirm their output and exit status before claiming work is complete. This gates completion on fresh evidence, not assumptions, ensuring your changes genuinely work.

Why should I run tests and builds before creating a pull request?▼

Running verification commands before a PR prevents false confidence and wasted rework. The skill enforces that every completion claim—tests pass, build succeeds, bug fixed—is backed by undeniable evidence from fresh command output, not guesswork or prior runs.

What's the best way to confirm a bug fix is complete?▼

Identify the verification command that validates the fix, run it in full, read the complete output and exit status, then verify your claim against that evidence. Only after confirmation should you declare success and commit or create a PR.

Can I skip verification if I'm confident my code works?▼

No. The skill explicitly counters common excuses like 'should work now' or 'I'm confident.' Fresh, explicit verification is mandatory—run commands, capture output, and confirm it before any completion claim.

Does verification-before-completion work across different codebases?▼

Yes. The skill applies across codebases by using the same gate workflow: identify your verification command, run it, read output and status, verify the claim against evidence, then complete. The process is agnostic to project structure or language.

Related Skills

Explore More Software Engineering Skills→
levanminhduclevanminhduc

Verification Before Completion

Run verification commands and analyze exit codes before reporting completion.

Community
Basic
NSObjectsNSObjects
4

verification-before-completion

Run full verification commands before declaring completion claims.

Community
Intermediate
adamayoungadamayoung
1

test

Execute unit test suites and capture diagnostic output via Xcode or make.

Community
Intermediate
HomericIntelligenceHomericIntelligence
6

verification

Run pytest, mypy, ruff, and pre-commit checks before declaring completion.

Official
Intermediate