What happens if I use words like 'probably' or 'seems to'?

The skill identifies these as Red Flags. It forces a stop to re-evaluate and run actual verification commands instead of relying on assumptions.

Can I use this for Regression Testing?

Yes, it specifically requires a Red-Green cycle where you must prove the test fails without the fix and passes with it to confirm the test's validity.

How does it handle linter and build checks?

It treats them as distinct gates; a passing linter does not imply a successful build. Each must be independently verified with its respective command and exit code.

What is the 'Iron Law' of this skill?

The Iron Law dictates that no completion claims can be made without fresh, verified evidence. If a verification command hasn't been run in the current context, the task cannot be claimed as finished.

Verified Completion Guardrail

Name: Verified Completion Guardrail
Author: claudiodearaujo

byclaudiodearaujo

•

Security & Testing

Enforces a strict verification protocol requiring fresh command output and evidence before any work is claimed as complete.

The Verified Completion Guardrail is a specialized skill designed to eliminate premature or false success claims during the development process. By implementing a 'Gate Function,' it mandates that any assertion of task completion, bug fixes, or passing builds must be accompanied by fresh, verifiable evidence from command executions. It prevents the use of vague language like 'should pass' and ensures that every change is validated against tests, linters, and requirements before being committed or merged, fostering a culture of technical honesty and reliability.

Key Features

01Strict TDD Red-Green cycle validation for regression testing

02Evidence-based verification patterns for tests, builds, and linters

031 GitHub stars

04Mandatory Gate Function for all completion claims

05Detection of 'false confidence' red flags in communication

06Checklist-based requirement verification and gap reporting

Use Cases

01Preventing broken builds by requiring fresh exit code verification before PR creation

02Standardizing quality control when delegating tasks to sub-agents or automation

03Ensuring regression tests are valid by verifying failure before the fix is applied

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/sistema-de-narra-o-de-livro verification-before-completion

For use in Claude.ai and ChatGPT

Download Skill

Key Features

01Strict TDD Red-Green cycle validation for regression testing

02Evidence-based verification patterns for tests, builds, and linters

031 GitHub stars

04Mandatory Gate Function for all completion claims

05Detection of 'false confidence' red flags in communication

06Checklist-based requirement verification and gap reporting

Use Cases

01Preventing broken builds by requiring fresh exit code verification before PR creation

02Standardizing quality control when delegating tasks to sub-agents or automation

03Ensuring regression tests are valid by verifying failure before the fix is applied

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/sistema-de-narra-o-de-livro verification-before-completion

For use in Claude.ai and ChatGPT

Download Skill