claude-code-starter

Start an autonomous implementation loop from a spec or PRD. Enters plan mode for user approval, enforces command gates (test/lint/typecheck/build), validates dependencies, commits incrementally, and maintains documentation and changelog. Production-ready quality gates.

Run a final release checklist before shipping. Verifies no TODOs, no debug code, docs updated, tests passing, dependencies justified, and security reviewed.

Document risks for changes touching auth, data, or migrations. Lists top risks, how to test/monitor them, and rollback strategy.

Maintain CHANGELOG.md with properly categorized entries. Use after implementing features, fixing bugs, or making any notable changes. Follows Keep a Changelog format.

Review code changes for quality, security, and best practices. Use when reviewing staged changes, pull requests, or specific files before merging.

Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.

Generate comprehensive tests for code. Use when adding test coverage, implementing TDD, or ensuring code reliability.

Install the pre-commit review hook that forces you to understand changes before committing. Use when you want to enable commit reviews or when setting up a new project.

Refactor code to improve clarity and maintainability without changing behavior. Use when improving readability, reducing complexity, or eliminating duplication.

Review recent changes and update CLAUDE.md to keep it relevant for future sessions. Use after significant changes or periodically to maintain context.

Review a merge request or branch. Compares a branch against main/master, summarizes changes, highlights concerns, and provides actionable feedback. Use for PR reviews or before merging.