ramzi1997-cmyk

Verify Change — Development skill for Claude Code

Development community

verify-change — drive it end-to-end; don't trust green tests.

How to install Verify Change

Installs to ~/.claude/skills/ramzi1997-cmyk-claude-code-production-kit-free-tier-verify-change/SKILL.md

Terminal

mkdir -p ~/.claude/skills/ramzi1997-cmyk-claude-code-production-kit-free-tier-verify-change && curl -fsSL https://raw.githubusercontent.com/ramzi1997-cmyk/claude-code-production-kit-free-tier/HEAD/skills/verify-change.md -o ~/.claude/skills/ramzi1997-cmyk-claude-code-production-kit-free-tier-verify-change/SKILL.md

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

What Verify Change does

verify-change — drive it end-to-end; don't trust green tests

Use before committing any nontrivial change to product code, especially right after tests go green.

The pitch

Green tests answer "does the code do what the tests say it should." They do not answer "can a real user actually reach this." Those are different claims, and the gap between them is one of the most common ways solo-built software quietly ships broken: every unit test passes, the agent reports success, and the featur

Alternatives in Development

Backpass — You don't write AGENTS.md 1.1k ★
Retune Color — Change a Graphite color safely by editing only the canonical primitive, then verify 452 ★
Benjamin Plus Skill — Benjamin-Plus: a measured token-efficiency skill for coding agents (−17.9% cost median, quality unchanged) 272 ★