verification-before-completion

Featured

Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed.

AI & Automation 1,596 stars 94 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

## Rules - Never claim "should work" without evidence - Never claim success without exit code 0 - Never claim a bug is fixed without reproduction failure - Always capture and report exit codes - Always run the full test suite, not just targeted tests - Use timeout guards (`timeout 60s`) to prevent hanging ## When to Use - Before completing any BUILD workflow step - Before claiming a DEBUG fix is verified - Before approving a REVIEW result - Before marking any task as done ## Agents Used - `integration-verifier` (primary consumer) - `component-builder` (TDD evidence) - `bug-investigator` (fix evidence)

Details

Author: a5c-ai
Repository: a5c-ai/babysitter
Created: 6 months ago
Last Updated: 2 days ago
Language: JavaScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed