For engineers using Claude: from test-first code to review, clean commit, PR & release.
Reach for this when you want the craft around a change to stay disciplined instead of rushed. It runs the whole arc: write code test-first with a full worked red-green-refactor cycle, enforce honestly strict TypeScript (the exact tsconfig flags plus a flag-by-flag migration path for loose codebases), self-review the diff as six ordered passes with concrete red flags, then turn it into a clean conventional commit, a reviewer-ready PR description, and a Keep-a-Changelog entry whose version bump follows mechanically from the categories - so the parts engineers get judged on come out consistent rather than improvised at the end.
Click to play with sound.
Arranged in the author's recommended order. Walk through them in sequence, or open any one on its own.
Write commit messages from a staged diff in Conventional Commits 1.0.0 format – correct type and scope, `!` and BREAKING CHANGE footers, GitHub closing keywords, and a body that explains why – and split mixed changes into separately revertable commits.
Write pull request titles and descriptions from a branch diff – problem and evidence, approach, risk and blast radius, real test evidence, rollout and rollback, a reviewer guide, before/after screenshots for UI, and correct closing keywords.
Generate or update a repository CHANGELOG.md in Keep a Changelog format from git history – grouping commits since the last tag into Added/Changed/Deprecated/Removed/Fixed/Security, rewriting them as user-facing entries.
Write or overhaul a project README from the repository itself – audience-first structure, a quickstart where every command is verified by running it or tracing it to CI, a configuration table built from the env vars the code reads, real troubleshooting.
Run a systematic multi-pass code review – correctness, design, security, performance, tests – and report findings ordered by severity with concrete, respectful suggestions.
Write and review TypeScript as if strict mode plus the hardening flags (noUncheckedIndexedAccess, exactOptionalPropertyTypes) are enforced, and migrate loose codebases to full strictness flag by flag without breaking the build.
Drive development with strict Red-Green-Refactor discipline – write one failing test, write the minimum code to pass it, refactor on green – including test-list planning and a worked kata cycle.
Behavioral guidelines to reduce common LLM coding mistakes: surface assumptions, keep it simple, make surgical changes, and define verifiable success criteria.