When should you use it?
- Review requests pile up faster than you can start them
- You don't want bots posting unchecked comments
- You have a Claude Code subscription
Not for: Repositories where sending code to a model provider isn't allowed; Teams that want fully automatic approvals
What do you need, and what do you get?
You need
- GitHub access to PRs requesting your review
- Claude Code CLI already signed in
- The open-source Cerber tool
You get
- A summary and change walkthrough per PR
- Draft inline comments
- A review you submit under your own account
How does it work, step by step?
- Install and connectRun Cerber locally with your GitHub access and existing Claude Code login.
- Let it watch requestsIt picks up PRs where you're a requested reviewer and prepares drafts.
- Read the walkthroughStart from the summary and change tour before reading the diff.
- Edit the findingsDiscuss, rewrite or drop each comment; nothing posts yet.
- Send as yourselfSubmit the review manually; auto-send is opt-in only for high-confidence approvals.
The prompt
Our own prompt, inspired by u/jtompl on r/ClaudeCode and written to work in Claude Code, Claude and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Review this pull request. Title and description: {pr_description}. Diff: {diff}. Repo conventions: {conventions}. Return: a three-sentence overview; a tour of the changes in reading order; and up to ten proposed inline comments with file, line, severity (blocker, should fix, nit) and suggested wording. Flag security, data migration and error-handling concerns first. Don't approve or post anything; these are drafts for me to edit.
Inspired by u/jtompl on r/ClaudeCode: I built a Claude Code review inbox for the PRs piling up behind me. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Drafts stay on your machine, but the code itself still goes to Anthropic for analysis; check your policy.
- Command execution is off by default; only trust authors or teams you know before enabling it.
Our take
The design choice that makes this worth trying is that the agent drafts and the human sends. Bot comments posted straight to a PR become someone else's problem, and teammates learn to ignore them. Keeping drafts local and posting under your name means every comment has an owner who has read it. Read-only by default is the other good decision: a review tool that can execute code from any PR author is an attack path, and Cerber makes you opt in per author, team or organization. Before adopting it at work, confirm that sending code to the model provider is allowed for your repositories. Use the walkthrough to orient yourself, but still read the critical parts of the diff, especially security, migrations and anything touching money. If you enable auto-send for approvals, set a high threshold and review a sample of what it approved. For teams, agree on whether reviews drafted this way should be labeled as AI-assisted.
Where the time goes back: The slow first read of every PR is done before you open it, and you spend time judging rather than starting.
FAQ
Will it post without me?
Where do drafts live?
Source and credit
Inspired by u/jtompl on r/ClaudeCode. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I built a Claude Code review inbox for the PRs piling up behind me
- Creator
- u/jtompl on r/ClaudeCode
- Published on
- Original date
- Sep 24, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.