Skill1.3k repo starsupdated today

verification-before-completion

This Claude Code skill enforces evidence-based verification by requiring concrete proof (exit codes, test results, logs) before claiming success on any task. Use it before completing build workflows, approving debug fixes, finalizing reviews, or marking tasks done to prevent unsubstantiated claims and ensure only demonstrable outcomes are reported.

View source Repository: babysitter

Install in Claude Code

Copy

git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/verification-before-completion && cp -r /tmp/verification-before-completion/library/methodologies/cc10x/skills/verification-before-completion ~/.claude/skills/verification-before-completion

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Verification Before Completion

## Overview

Enforces the evidence-first principle: every claim of success, fix, or completion must be backed by concrete evidence. Exit codes, test output, and logs are the only acceptable proof.

## Evidence Types

1. **Exit codes**: zero = success, non-zero = failure
2. **Test output**: pass/fail counts, coverage percentages
3. **Logs**: error messages, stack traces, resolution confirmation
4. **Build output**: compilation success/failure with timestamps

## 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)