review-pr-companionlisted

Package a code review as a review branch -- small, reviewer-shaped fix commits plus a REVIEW_HANDOFF.md written for the author's coding agent -- pushed for the author to integrate, with no pull request opened. Use when reviewing a pull request or a local branch and you want to hand back working commits and the reasoning behind them, not just inline comments.
richardkmichael/claude-rodin · ★ 0 · Code & Development · score 72

Install: claude install-skill richardkmichael/claude-rodin

# Review-PR Companion Turn a code review into a branch the author can integrate directly. Instead of leaving comments and waiting for someone to re-derive the fixes, you deliver: - a review branch of small, reviewer-shaped commits for the agreed fixes; - `REVIEW_PLAN.md`, the reviewer's document: numbered items, the reasoning behind each, and follow-ups; - `REVIEW_HANDOFF.md`, whose whole audience is the author's coding agent; - optional follow-up specs for work deliberately left out of scope; and - a drafted review comment linking the branch and its compare view. The premise: the fastest way to discuss code is a diff plus a briefing the other side's agent can read. Make no commits until the reviewer approves the plan. ## 1. Locate the target and create the review branch The target is a GitHub pull request (a number or URL) or a local branch with no PR. For a pull request, fetch the head commit through the PR ref using git: ```bash git fetch origin pull/<N>/head # refs/pull/<N>/head -- the PR's current tip ``` `refs/pull/<N>/head` is a read-only ref GitHub keeps on the base repo, pointing at the PR's tip whether the source branch lives on this repo or on a fork. The source branch by name (`git fetch origin <headRefName>`) only exists on the base repo for same-repo pull requests, so prefer the PR ref -- it is fork-proof and needs only `origin`. The PR ref gives you the commit, not the branch name. Read the name and author from `gh` when it is installed; it is