skills.rest
Jhabbig
JhabbigCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Verify work completion against fresh command output and execution evidence.

Updated Apr 5, 2026
Search Tags:#testing#quality assurance#verification#evidence#regression#build validation
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill verification-before-completion-jhabbig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/Jhabbig/Habbig --skill verification-before-completion-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false completion claims by forcing fresh verification before any statement that work is done, fixed, or passing.

Core Features & Use Cases

  • Evidence-first confirmation: Run the exact command that proves a claim and inspect the live output before reporting success.
  • Build and test validation: Use it when checking tests, builds, bug fixes, regression results, or any status that depends on execution evidence.
  • Use Case: Before saying a feature is complete, verify the relevant test suite or build command and only then communicate the result.

Quick Start

Use the verification-before-completion skill to run the relevant check and report the fresh output before claiming the work is complete.

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 build validation and test results before claiming a task is complete?▼

Build validation requires running the exact validating command and inspecting live output and exit codes. You verify test results by reading fresh execution evidence and refusing completion claims without direct proof of current runtime success.

What is evidence-first confirmation for software testing and bug fixes?▼

Evidence-first confirmation is the process of running the exact command that proves a claim and inspecting the live output before reporting success. It ensures bug fixes and testing status depend on current execution evidence rather than assumptions.

Why does my workflow report false completion claims for regression checks?▼

False completion claims happen when success is reported without fresh verification. Regression checks require running the full validating command, reading failures and exit codes, and refusing completion until direct runtime proof confirms the fix.

How do I enforce test suite execution before marking a feature as done?▼

Enforce test suite execution by requiring the relevant build or test command to run and produce fresh output. You mark a feature done only after reading the exit codes and execution evidence to confirm passing results.

Can I use this verification approach for any workflow depending on runtime execution evidence?▼

Yes, you can apply this verification approach to any workflow where success depends on current runtime results. It works for builds, bug fixes, regression checks, and testing by requiring fresh command output before any completion status is communicated.

Related Skills

Explore More Software Engineering Skills→
tyk-labtyk-lab

verification-before-completion

Run the full verification command and report exit codes and logs.

Community
Intermediate
droxeydroxey
1

verification-before-completion

Require fresh verification evidence before claiming completion in software delivery workflows.

Community
Basic
JaronTamJaronTam

bmad-testarch-test-review

Review test suites against best practices and generate quality reports.

Community
Advanced
breakingcircuits1337breakingcircuits1337

verification-before-completion

Verify command outputs before claiming task completion.

Community
Basic