verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: sciman-top

Verify completion claims with the smallest sufficient evidence before reporting.

Updated Mar 26, 2026

Search Tags:#code quality #testing #validation #verification #evidence #completion claim #test receipt

Ready to run

npx skills add https://github.com/sciman-top/skills-manager --skill verification-before-completion-sciman-top

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/sciman-top/skills-manager/tree/main/overrides/patches/verification-before-completion
Command: npx skills add https://github.com/sciman-top/skills-manager --skill verification-before-completion-sciman-top

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents premature or unsupported completion claims by requiring fresh, proportionate evidence that directly proves the exact claim before it is reported. ## Core Features & Use Cases - Claim-scoped verification: State the exact claim and select the cheapest command or current receipt that directly proves it. - Receipt reuse: Reuse an exact-current passed receipt when its source fingerprint and dirty policy match, avoiding redundant test runs. - Bounded escalation: Escalate to broader gates only for an independent failure mode, a shared or high-risk seam, or an explicit repository closeout contract. - Use Case: After fixing a bug, run only the focused affected check, read the exit code, and report the proven boundary distinguishing repository verification from host load and live acceptance. ## Quick Start Use the verification-before-completion skill to prove my fix works with the smallest sufficient check before I report it as done.

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 a fix before claiming completion?▼

State the exact claim, then select the cheapest command or current receipt that directly proves it. Run the focused affected check, read the exit code and failure count, and report only the proven boundary.

When can I reuse a previous test receipt instead of rerunning tests?▼

Reuse a passed receipt only when it is exact-current, meaning its source fingerprint and dirty policy match the current state. Otherwise run the focused affected check to produce fresh evidence.

When should verification escalate to a full test suite or CI run?▼

Escalate only for a current independent failure mode, a shared or high-risk seam, or an explicit repository closeout contract. The skill does not authorize broader gates, network probes, or host mutation without such a reason.

What is the difference between repository verification and live acceptance?▼

Repository verification proves code passes checks in the repo, while live acceptance confirms real invocation and external effects in the host environment. The skill requires reporting which boundary was actually proven.

What should I re-run after applying a fix?▼

Re-run only the layer invalidated by the fix, once inputs are frozen. Run each required layer once and stop when the declared claim is proven, rather than repeating the full audit.