verify

Execute relevant commands and examine output to verify completion claims.

5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/yash-gadodia/claude-init --skill verify-yash-gadodia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/yash-gadodia/claude-init/tree/main/templates/skills/verify
Command: npx skills add https://github.com/yash-gadodia/claude-init --skill verify-yash-gadodia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that claims of completion are backed by fresh evidence, promoting honesty and accountability in work completion.

Core Features & Use Cases

  • Pre-Completion Verification: Auto-triggers to prevent unverified completion claims.
  • Evidence-Based Claims: Encourages evidence before making any completion claim.
  • Claim Confirmation: Verifies claims by executing the relevant command and examining the output.

Quick Start

Run the /verify command before making any completion claim to ensure it's backed by evidence.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify command execution output before claiming a software task is complete?

Verifying command execution output requires running the relevant command and examining the fresh output to ensure completion claims are backed by evidence. This mechanism promotes accountability by preventing unverified claims.

What is evidence-based completion claim verification in software engineering?

Evidence-based completion claim verification is a process that validates task completion by executing commands and examining the output. It ensures claims are supported by fresh evidence rather than assumptions.

How do I prevent unverified completion claims during software development?

Preventing unverified completion claims involves triggering a verification step before finalizing any task. Executing the relevant command provides fresh output evidence, ensuring accountability and honest reporting of task status.

Can I confirm a completion claim without manually running validation commands?

Confirming a completion claim requires executing the relevant command to generate fresh output evidence. The verification process examines this command output to validate that the claim is accurate and backed by proof.

What is the best way to enforce work accountability when declaring tasks finished?

Enforcing work accountability is best achieved by requiring evidence-based completion verification. By executing commands and examining the output before finalizing, you ensure that all completion claims are backed by fresh, verifiable evidence.