Cmd PR Review Prepare
Prepare branch for code review by building context, identifying issues, and suggesting improvements
Install
/plugin marketplace add Olshansk/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Olshansk/agent-skills --skill cmd-pr-review-preparegit clone --depth 1 https://github.com/Olshansk/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/cmd-pr-review-prepare ~/.claude/skills/cmd-pr-review-preparePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Review Preparation Agent Your goal is to help me do a code review as we pick up work from a branch we worked on previously. You are one of my code reviewing buddies for this branch. Note that you may be one of several instances of Claude Code that I'm using in parallel to review this branch. Along the way, don't hesitate to ask questions and build plans. Be pragmatic. Don't over engineer or write long unnecessary documentation. ## Determine Scope **Default (no scope specified):** diff the current branch against the repo's base branch. Detect the base branch in order — stop at the first success: 1. `gh repo view --json defaultBranchRef -q '.defaultBranchRef.name' 2>/dev/null` 2. `git remote show origin 2>/dev/null | grep "HEAD branch" | cut -d: -f2 | xargs` 3. `git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'` Do **not** assume `main` or `master`. If all methods fail, ask the user. Once resolved, run: ```bash git diff <base>...HEAD -- ":(exclude)*.lock" ":(exclude)package-lock.json" ":(exclude)pnpm-lock.yaml" ":(exclude)package.json" ``` **If the user specifies a scope**, use the corresponding command instead: | Scope | Command | What it covers | |---|---|---| | `unstaged` | `git diff HEAD -- <excludes>` | All uncommitted changes (staged + unstaged) | | `last commit` / `last 1 commit` | `git diff HEAD~1...HEAD -- <excludes>` | Changes in the most recent commit |
Details
- Skill name
cmd-pr-review-prepare- Repository
- Olshansk/agent-skills
- Path
skills/cmd-pr-review-prepare/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Cmd PR Review Prepare skill do?
Prepare branch for code review by building context, identifying issues, and suggesting improvements
How do I install the Cmd PR Review Prepare skill?
Claude Code plugin: /plugin marketplace add Olshansk/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cmd PR Review Prepare popular?
It lives in Olshansk/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Cmd Agent Persona Set
9Olshansk/agent-skills
Prime the agent with a behavioral persona for the conversation
Cmd Clean Code
9Olshansk/agent-skills
Improve code readability without altering functionality using idiomatic best practices
Cmd Code What
9Olshansk/agent-skills
Catch the user up on what the agent has been doing in the current session with 3-5 ultra-tight bullet points. Use when the user invokes /cmd-what, asks "what are you doing", "what did you do", "catch me up", "status", "where are we", or otherwise needs a fast situational summary of in-flight agent work.
Cmd PR Scope Sweep
9Olshansk/agent-skills
Final pass to identify missed items, edge cases, and risks before considering a scope done
Cmd PR Gh Comments
9Olshansk/agent-skills
Holistically triage and resolve GitHub PR review comments — gather comments with full line ranges, study surrounding code context (TODOs, docstrings, related logic), hunt for adjacent improvements via rg, execute an approval-gated plan, optionally refine AGENTS.md style rules, and propose cmd-olshanskify template updates when feedback comes from @olshansk
PR Review
9borkweb/skills
Review a GitHub PR and post its CRITICAL findings as line-anchored inline comments with suggestion blocks after you confirm; INFORMATIONAL findings stay in chat. Adds a second pass from the other harness when the diff needs one, reuses CI results, and reviews only new commits on a re-run. Invoke only when the user explicitly asks for /pr-review or for a PR review that posts comments, or when bork:do runs a review batch; never on your own. For a local diff or branch without posting, use review.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.