skills.rest
DYAI2025
DYAI2025COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Verify task status with fresh test, build, lint, and regression evidence.

3|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/DYAI2025/Stoppclock-page --skill verification-before-completion-dyai2025
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/DYAI2025/Stoppclock-page/tree/main/stoppclock_speckit/.claude/commands/SKILL (15).md
Command: npx skills add https://github.com/DYAI2025/Stoppclock-page --skill verification-before-completion-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the costly and trust-eroding issue of claiming work is complete or correct without actual verification. It enforces a strict "evidence before assertions" rule, ensuring all success claims are backed by fresh, explicit proof.

Core Features & Use Cases

  • Mandatory Verification Gate: Requires running and confirming output of verification commands before any completion claim.
  • Rationalization Prevention: Identifies and counters common excuses for skipping verification.
  • Use Case: Ensure every bug fix, feature implementation, or test run is genuinely complete and correct before committing, creating a PR, or reporting status, thereby building trust and reducing rework.

Quick Start

BEFORE claiming any status or expressing satisfaction:

1. IDENTIFY: What command proves this claim?

2. RUN: Execute the FULL command (fresh, complete)

3. READ: Full output, check exit code, count failures

4. VERIFY: Does output confirm the claim?

5. ONLY THEN: Make the claim

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 that my code changes are actually complete before committing?▼

Verification means running the full test, build, and linting commands fresh, reading their complete output, checking exit codes, and confirming success before making any completion claim. Skip this step and you risk committing broken code that breaks trust and causes rework.

What commands should I run to verify a bug fix or feature is ready?▼

Execute the full verification pipeline: run tests with output capture, build the project completely, run linters, and check for regressions. Examine each exit code and output line; a single failure means the work is not complete, regardless of how confident you feel.

Why do developers skip verification steps, and how do I avoid it?▼

Common rationalizations include "I'm sure it works" or "tests passed locally before." Counter these by making verification mandatory before any status claim. Document what command proves each claim, run it fresh every time, and base assertions only on evidence from that run.

Can verification prevent pull request rejections and rework?▼

Yes. Verification catches failures before PR submission, ensuring every commit is genuinely correct. This eliminates rejected reviews, reduces reviewer burden, and builds confidence in code quality across the team.

What happens if verification output shows failures or warnings?▼

Do not claim the work is complete. Address every failure or warning, re-run the full verification suite again, and confirm all outputs pass before proceeding with commits or pull requests.

Related Skills

iankikuiankiku
18

gate

Run lint, typecheck, build, and test cycles with automatic fixes.

Community
Advanced
mattsp1290mattsp1290

ship

Coordinate review, fix, verify, commit, push, and pull request processes.

Community
Advanced
krzemienskikrzemienski
2

verification-before-completion

Require fresh verification evidence before declaring task completion.

Community
Advanced
robertphyattrobertphyatt
7

testing-theatre-detection

Detect missing assertions, excessive mocking, and swallowed errors in JavaScript and Python test suites.

Community
Advanced