Draft PR reviews, then send them yourself
They used Claude Code to prepare GitHub review drafts for queued pull requests, while keeping final edits and submission under their control.
- What they did
- They built Cerber to watch GitHub for pull requests that asked for their review. It ran Claude Code through their existing CLI login and created draft reviews in a local web interface. The drafts included a summary, a walkthrough of the changes, and suggested inline comments, and they could talk through the findings, rewrite them, or remove them before sending.
- How it went
- It helped them get through a backlog that had reached 15 pull requests. It also kept AI comments from going straight to GitHub without review. The tradeoffs were that code still went to Anthropic, the setup required a paid Claude Code subscription, and approvals only auto-send if they are opted in and pass a confidence check.
- Tips
- Keep the final send step manual if you want a review buffer between the agent and GitHub. Treat local drafts as a working queue, and use read-only execution unless you fully trust the repo author or organization.
Try it yourself with Claude Code
Check the open pull requests in [repository] that are waiting on my review. For each one, read the diff and prepare a review draft with a short summary, a change-by-change walkthrough, and inline comments ordered by importance. Save each draft to [location] so I can edit it later. Do not post, approve, or delete anything; stop and ask me before any action that would send, submit, or remove a review. When all drafts are ready, tell me which PRs you covered.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Build a lean skill layer from CLI help output
A developer swapped token-heavy Jira and GitLab MCPs for Markdown-based skills generated from the Atlassian and GitLab CLIs.
Use Claude Code to revive an old assembly build
A developer used Claude Code to get a 1991 assembly game’s old tools compiling again on modern setup files.
Share files between sandboxed Claude Code agents through MCP
A developer connected sandboxed Claude Code instances to a virtual file system so they could pass files through MCP without direct access to AWS.
Use Claude Code to plan and run a legacy stack migration
An engineer used Claude Code to map, split, and execute a multi-repo migration while keeping each step tied to docs, tickets, and review.
Investigate why a service is getting killed
Run a read-only SSH check to find the cause of a process death and rank fixes by risk.
Use a browser agent to find and fix UI bugs
A frontend developer uses a browser agent and a coding agent together to spot UI issues, trace them in Chrome, and patch the code.