How does this skill improve the development workflow?

It eliminates 'false positives' and assumptions, ensuring that every piece of code is actually tested and functional before it reaches the repository, saving time on rework.

Does this skill work with automated test suites?

Yes, it is specifically designed to mandate the running of test suites and requires the agent to read and confirm the exit codes and failure counts before proceeding.

What is the main purpose of the Verified Completion Guard skill?

It prevents Claude from claiming a task is finished without first running and confirming the actual output of verification commands like tests, linters, or build scripts.

When should I use this skill in my coding session?

It should be used immediately before committing code, opening a Pull Request, or moving on to a new feature to ensure the current work is 100% complete.

Verified Completion Guard

Name: Verified Completion Guard
Author: jrc1883

byjrc1883

Seguridad y Pruebas

Enforces rigorous, evidence-based verification protocols to ensure code changes are fully validated before being marked as complete.

Acerca de

The Verified Completion Guard skill implements a strict 'evidence before assertions' workflow for Claude Code, preventing premature claims of success or completion. It acts as a mandatory cognitive gatekeeper that requires fresh execution of test suites, linters, and build commands before any work is committed, merged, or reported as finished. By eliminating the reliance on assumptions or 'should work' logic, this skill ensures that every claim of success is backed by real-time terminal output, significantly reducing the risk of shipping broken code or missing requirements.

Características Principales

Standardized gate function for all status updates and PRs
0 GitHub stars
Prevention of 'hallucinated' success in autonomous agent tasks
Mandatory 'Evidence Before Claims' verification protocol
Comprehensive checklist for multi-requirement feature validation
Automated red-green regression test validation requirements

Casos de Uso

Ensuring zero-error linter and build states before creating a Pull Request
Double-checking automated agent output against version control diffs before final approval
Validating bug fixes through rigorous reproduction and regression testing cycles

Acerca de

Características Principales

Standardized gate function for all status updates and PRs
0 GitHub stars
Prevention of 'hallucinated' success in autonomous agent tasks
Mandatory 'Evidence Before Claims' verification protocol
Comprehensive checklist for multi-requirement feature validation
Automated red-green regression test validation requirements

Casos de Uso

Ensuring zero-error linter and build states before creating a Pull Request
Double-checking automated agent output against version control diffs before final approval
Validating bug fixes through rigorous reproduction and regression testing cycles