chrisryugj

Verification Before Completion — Development skill for Claude Code

Development community

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence.

How to install Verification Before Completion

Installs to ~/.claude/skills/chrisryugj-lexdiff-verification-before-completion/SKILL.md

Terminal
mkdir -p ~/.claude/skills/chrisryugj-lexdiff-verification-before-completion && curl -fsSL https://raw.githubusercontent.com/chrisryugj/lexdiff/HEAD/.claude/skills/verification-before-completion.md -o ~/.claude/skills/chrisryugj-lexdiff-verification-before-completion/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Verification Before Completion does


name: verification-before-completion description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Verification Before Completion

Overview

Claiming work is complete without verification is dishonesty, not efficiency.

**Core principle:** Evidence before claims, always.

**Violating the letter of this rule

Alternatives in Development

  • Implement Plan — You are tasked with implementing an approved technical plan from thoughts/shared/plans/ 10k ★
  • MCP Edit — tilth_write replaces the host Edit and Write tools 349 ★
  • Pair Verify — Use after you fix a bug and before you claim it fixed — it spawns ONE skeptic sibling session via CCC that mus 130 ★

Full documentation available on GitHub

View Source Repository