Write the code review yourself and let Claude format the GitHub comments
At a glance
A Lobsters commenter reviews changes locally, records findings in Markdown and uses Claude Code to format the GitHub review. This workflow is listed under Code Review, Developer Workflow, GitHub.
- Agents / tools
- Claude Code, Git, GitHub, VS Code, Zed
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Have a Git checkout of the proposed change, VS Code or Zed for viewing diffs, and Claude Code with the access needed to post a review to GitHub. Use a separate review checkout so your own unfinished edits are not mixed in. 2) Pull the proposed change and reset back to its base while keeping the proposed changes in the working tree. This makes the entire change available for local diff review. 3) Read the diff in the editor and stage portions as you finish examining them. Write your own review observations in a Markdown file as you go. 4) Give that file to Claude Code to format into GitHub line comments and the review body, and post the resulting review. The commenter explicitly retains authorship of the findings.
Worth knowing
The AI handles formatting and posting in this account. The commenter does not delegate the technical judgment or the writing of the review findings.