skills.rest
allanninal
allanninalCOMMUNITY
Explore all skills by this author →
Website𝕏@allanninGitHub

verification-before-completion

Run verification commands and review output before reporting task completion.

1|Updated Jan 31, 2026
Search Tags:#workflow#testing#quality assurance#code review#verification#completion
One-click install
npx skills add https://github.com/allanninal/claude-code-skills --skill verification-before-completion-allanninal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/allanninal/claude-code-skills/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/allanninal/claude-code-skills --skill verification-before-completion-allanninal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of task completion, bug fixes, or successful test runs by enforcing a strict verification process before any assertion of success is made.

Core Features & Use Cases

  • Mandatory Verification: Ensures that commands proving a claim are executed and their output is reviewed.
  • Evidence-Based Claims: Promotes a culture of honesty and accuracy by requiring concrete evidence before stating work is done.
  • Use Case: Before declaring a bug fixed, you must run the specific test that previously failed and confirm it now passes, presenting the output as proof.

Quick Start

Before claiming any status or expressing satisfaction, identify and run the command that proves the claim, then verify its output.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I enforce verification before claiming code review or testing completion?▼

Enforce verification before completion by running explicit commands that prove your claim and reviewing their output to confirm success before reporting any task or testing status.

What is an evidence-based verification policy for software engineering workflows?▼

An evidence-based verification policy requires running explicit commands and reviewing their output to confirm success before making any claims about task completion, bug fixes, or deployment status.

How do I stop premature claims of bug fixes during development?▼

Stop premature bug fix claims by running the specific test that previously failed and confirming it passes, presenting the output as proof before declaring the issue resolved.

Does strict verification work without external testing dependencies?▼

Yes, strict verification works without external dependencies by enforcing a process that requires running available commands and manually reviewing their output to confirm status claims.

When do I need to run verification commands during deployment?▼

You need to run verification commands during deployment whenever you are ready to claim success, ensuring you execute proof commands and review their output before communicating completion status.

What is the best way to verify task completion before reporting status?▼

The best way to verify task completion is identifying and running the specific command that proves your claim, then reviewing its output to confirm success before asserting work is done.

Related Skills

Explore More Software Engineering Skills→
jpoutrinjpoutrin
14

qa-testing-methodology

Design test cases for happy path, validation, edge, error, and permission scenarios.

Community
Basic
mrtolkienmrtolkien
5

verification-before-completion

Run verification commands and report results with attached evidence.

Community
Intermediate
billydeeii136billydeeii136

health

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

Community
Intermediate
elophantoelophanto
116

verification-before-completion

Execute verification commands and report pass/fail with evidence before completion.

Community
Advanced