verification-before-completion

Verify command output before claiming task completion.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xxih/ai-harness-zh --skill verification-before-completion-xxih
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/xxih/ai-harness-zh/tree/main/references/translations/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/xxih/ai-harness-zh --skill verification-before-completion-xxih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often claim tasks are finished without concrete evidence, leading to silent failures, rework, and loss of trust.

Core Features & Use Cases

  • Evidence‑First Rule: Requires a fresh verification command and its output before any completion claim.
  • Four‑Step Process: Identify the appropriate command, run it, read the full output, and verify that the result truly supports the claim.
  • Applicable Scenarios: Commits, pull‑request creation, task handoffs, and any moment a developer or agent states that work is complete.

Quick Start

Use the verification-before-completion skill to run the four‑step verification process before submitting a commit or opening a PR.

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 before a commit or pull request?

To verify work before a commit or pull request, identify the appropriate verification command, run it, read the full output, and verify the result supports your completion claim.

What does evidence-based task completion mean?

Evidence-based task completion requires running a fresh verification command and checking its output before claiming any task is finished, preventing silent failures and rework.

Why should I validate task completion before handing off work?

Validating task completion before handing off work enforces an evidence-first rule, ensuring silent failures are caught and trust is maintained through verified command output.

What is the four-step verification process for pull requests?

The four-step verification process for pull requests involves identifying the correct command, executing it, reading the full output, and verifying the result supports the success claim.

When do I need to apply pre-commit verification?

Apply pre-commit verification during commits, pull-request creation, and task handoffs to ensure that concrete command execution evidence supports any stated success claim.