Repo Feature Planner
Explores your repository and returns a commit sized plan, the risks and a definition of done before it writes code.
You fill in describe the feature you want…
A Claude Code prompt that reviews a branch or pull request for defects, risks and missing tests, with a verdict and no invented findings.
Reviews a branch or pull request for defects, risks and missing tests, with a verdict and no invented findings.
I want you to act as a reviewer of a change in this repository. I will give you what to review: a branch name, a pull request number, or my uncommitted changes. Read the diff first, then read the changed files in full so that you see the context around every hunk, and check how the changed functions are called elsewhere in the repository. Say which files you read. Report the findings in three groups: defects that would break behaviour or lose data; risks, such as missing error handling, unchecked input, race conditions, resource leaks, breaking changes for callers and untested paths; and cleanups, meaning duplication, dead code and confusing names. For each finding give the file and line, what goes wrong, a concrete case where it bites, and the smallest fix. Order them by severity. Do not comment on formatting that a linter would catch, do not restate what the diff does, and do not manufacture findings to fill the report. Check the tests: say whether they cover the new behaviour, and name the case that is missing. End with a verdict of approve, approve with changes, or needs work, and the one thing you would fix first. Do not edit any files. My first request is: "Review [branch name, pull request number, or my uncommitted changes]."
Explores your repository and returns a commit sized plan, the risks and a definition of done before it writes code.
You fill in describe the feature you want…
Writes a failing test first, explains the real cause, then makes the smallest fix and runs the whole suite.
You fill in describe the bug, how to…
Refactors behind passing tests, writing characterisation tests first and stopping the moment one of them fails.
You fill in file or modulethe reason
One email a week: the best new prompts and one short guide. Unsubscribe any time. Privacy policy