skills.rest
qiushibang
qiushibangCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run fresh verification commands and review full output before completion claims.

Updated Jun 2, 2026
Search Tags:#code quality#workflow#testing#software development#verification#guardrails#completion claims
One-click install
npx skills add https://github.com/qiushibang/skill-creator-pro --skill verification-before-completion-qiushibang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/qiushibang/skill-creator-pro/tree/main/references/superpowers/verification-before-completion
Command: npx skills add https://github.com/qiushibang/skill-creator-pro --skill verification-before-completion-qiushibang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the critical risk of false work completion claims that lead to broken code, missed requirements, wasted rework, and broken trust with team members or stakeholders, which occurs when teams skip verification before declaring tasks, fixes, or features done.

Core Features & Use Cases

  • Mandatory 5-Step Verification Gate: Enforces a non-negotiable process to identify the correct verification command, run it fresh, review full output, and only make claims if evidence supports the statement.
  • Common Failure & Red Flag Reference: Lists typical false claim patterns (e.g., trusting agent success reports, relying on partial checks) and explicit red flags that require immediate work stoppage.
  • Rationalization Prevention: Blocks common excuses for skipping verification (e.g., "I'm confident", "just this once") with clear reality checks to eliminate shortcuts.
  • Use Case: A developer about to push a bug fix can use this skill to run the full test suite, confirm 0 failures, and only then claim the fix is complete, avoiding shipping broken code to production.

Quick Start

When you are about to claim a task, code change, test run, or feature is complete, activate this skill to run the required verification command, review the full output, and only make your claim if the evidence supports it.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent false work completion claims when delivering code changes?▼

To prevent false work completion claims, enforce a mandatory verification gate that requires running the correct verification command fresh, reviewing the full output, and only claiming completion if the evidence explicitly supports it.

Why do developers ship broken code even when they claim a bug fix is complete?▼

Developers ship broken code because they rely on partial checks or agent success reports instead of fresh verification. Common rationalizations like high confidence lead to skipped test execution and missed requirement compliance before declaring work done.

What is the best workflow for verifying requirement compliance before declaring a task done?▼

The best verification workflow involves a non-negotiable 5-step gate: identify the specific verification command, execute it fresh, review the entire output, stop work if red flags appear, and make evidence-backed claims only when tests show zero failures.

How do I stop skipping test execution before pushing a bug fix?▼

You stop skipping test execution by applying rationalization prevention checks that block common excuses like "just this once". This enforces a reality check requiring fresh command execution and full output review before pushing any code.

What are common red flags that should stop task delivery immediately?▼

Common red flags requiring immediate work stoppage include trusting agent success reports without fresh execution, relying on partial checks, and claiming completion based on confidence rather than reviewed test output evidence.

Does this verification workflow apply to all software development tasks?▼

Yes, this verification workflow applies to all software development, QA, and task delivery scenarios. It enforces fresh command execution and evidence-backed claims whenever you need to verify tests, builds, bug fixes, or requirement compliance before declaring work done.

Related Skills

Explore More Software Engineering Skills→
northseadlnorthseadl

verification-before-completion

Enforces running verification commands before claiming completion or success.

Community
Advanced
Probably-GroupProbably-Group
3

verification-gate

Verify completion claims with fresh test, build, lint, and type checks.

Official
Advanced
udsy19udsy19

ci-cd-and-automation

Automate CI/CD pipeline setup with linting, testing, and security checks.

Community
Advanced
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate