skills.rest
danger-English
danger-EnglishCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and validate outputs before completion claims.

2|Updated May 13, 2026
Search Tags:#workflow#verification#evidence#quality-assurance#guardrails#pull-request#tests
One-click install
npx skills add https://github.com/danger-English/claude-code-intro --skill verification-before-completion-danger-english
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/danger-English/claude-code-intro/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/danger-English/claude-code-intro --skill verification-before-completion-danger-english

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces verification before declaring completion by requiring fresh evidence. The approach ensures that no success claim is made without running the verification command, reading its full output, and validating the result against a defined standard.

Core Features & Use Cases

  • Guides teams through a structured verification workflow that identifies the proving command, executes it freshly, and reviews outputs.
  • Enforces evidence collection and explicit validation before PRs or commits.
  • Provides auditable results that can be attached to pull requests or release notes.

Quick Start

Identify the verification command, run it with fresh data, and report the results with evidence before making any completion 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 enforce verification before claiming a pull request is complete?▼

To enforce verification before claiming a pull request is complete, you must run the proving command freshly, read its full output, and validate the result against a defined standard. This structured workflow prevents unverified success claims.

What is the best way to require fresh evidence for quality assurance before a commit?▼

The best way to require fresh evidence for quality assurance is to execute verification commands and evaluate their outputs immediately before a commit. This ensures integrity and accountability by preventing completion claims without validated evidence.

How do I attach auditable test results to a pull request?▼

To attach auditable test results to a pull request, run your verification commands freshly and report the evaluated outcomes. This provides explicit validation evidence that can be directly attached to pull requests or release notes.

Does this verification workflow work for any success claim or only pull requests?▼

This verification workflow applies to any success claim, not only pull requests. It enforces evidence collection and explicit validation across commits, releases, or any scenario requiring integrity and accountability before completion is declared.

Why should I run verification commands with fresh data instead of relying on previous results?▼

Running verification commands with fresh data is necessary to ensure integrity and accountability. Relying on previous results risks making a success claim without verified evidence, bypassing the structured validation needed to prove actual completion.

Related Skills

Explore More Software Engineering Skills→
lagz0nelagz0ne
2

verification-before-completion

Enforce fresh verification evidence before claiming work completion.

Community
Basic
pcsensorpcsensor

verification-before-completion

Enforce verified evidence before declaring PR, merge, or release completion.

Community
Intermediate
Monjyu1101Monjyu1101
1

requesting-code-review

Automate pre-commit code verification with security scans, quality gates, and auto-fixes.

Community
Advanced
1337hero1337hero
1

verification-before-completion

Run full verification commands and report evidence before claiming completion.

Community
Advanced