skills.rest
woodrowpearson
woodrowpearsonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Verify completion claims by running proving commands and validating results.

Updated Jul 14, 2025
Search Tags:#verification#completion#evidence#quality-assurance#tests#checks
One-click install
npx skills add https://github.com/woodrowpearson/mids-hero-web --skill verification-before-completion-woodrowpearson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/woodrowpearson/mids-hero-web/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/woodrowpearson/mids-hero-web --skill verification-before-completion-woodrowpearson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that any claim of completed work is supported by fresh verification evidence, preventing misleading statements and unnecessary rework.

Core Features & Use Cases

  • Evidence-driven claims: Before declaring completion, collect and present fresh verification outputs (test results, lint outputs, or CI status).
  • Rule-based gatekeeping: Enforces a step-by-step workflow: identify proving command, run fully, read output, verify evidence, and only then declare success.
  • Use Case: Before merging a PR, run the verification sequence to confirm that tests pass and no critical issues remain.

Quick Start

Run the verification workflow by executing the steps: identify the command that proves completion, run it in full, review the results for exit codes and failures, confirm the evidence, and then safely declare completion with a summary of the verification outputs.

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 task completion with evidence before merging a PR?▼

To verify completion before merging a PR, identify the proving command, execute it fully, and validate the test results or lint outputs before declaring success.

What is evidence-driven verification in software QA workflows?▼

Evidence-driven verification is a QA workflow that requires fresh verification outputs, such as test results or CI status, to back up any claims of completed work before success is declared.

How do I run a verification sequence to prevent misleading completion claims?▼

Run a verification sequence by identifying the command that proves completion, executing it fully, reviewing the exit codes and failures, and confirming the evidence before declaring success.

Can I use verification checks for quality assurance without external dependencies?▼

Yes, you can apply verification checks to QA workflows without external dependencies by running a rule-based gatekeeping process that validates fresh outputs directly.

What is the best way to enforce step-by-step verification before declaring success?▼

The best way to enforce verification is to apply a three-step approach: identify the proving command, execute it fully, and validate the results before declaring any task a success.

Why does declaring completion without fresh test results cause unnecessary rework?▼

Declaring completion without fresh test results causes rework because misleading statements are made when success claims are not backed by freshly validated verification evidence.

Related Skills

Explore More Software Engineering Skills→
dolutechdolutech
6

verification-before-completion

Run verification commands and report fresh outputs before declaring completion.

Community
Advanced
HerbertJulioHerbertJulio
20

verify

Execute verification workflows and validate command outputs against gate criteria.

Community
Advanced
billydeeii136billydeeii136

health

Compute a weighted 0-10 codebase health score and track trends over time.

Community
Intermediate
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate