mcpbeat

Review Pr

tobihagemann/review-pr

Review a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to \"review PR\", \"review pull request\", \"review this PR\", \"check PR before merging\", or \"full PR review\".

383 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
398
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/tobihagemann/turbo --skill review-pr

The instruction itself

8 sections, as written by the author

Review PR

Fetch PR context, run a comprehensive code review, evaluate findings, and dispatch accepted findings to implementation.

Task Tracking

At the start, use TaskCreate to create a task for each step:

  • Run /fetch-pr-comments skill
  • Detect base branch
  • Run /review-code skill
  • Run /evaluate-findings skill
  • Run /resolve-findings skill

Step 1: Run /fetch-pr-comments Skill

Run the /fetch-pr-comments skill to get unresolved review comments.

Step 2: Detect Base Branch

Detect the PR's base branch via gh pr view --json baseRefName --jq '.baseRefName'.

Step 3: Run /review-code Skill

Run the /review-code skill. The diff command is git diff <base-branch>...HEAD.

Step 4: Run /evaluate-findings Skill

Run the /evaluate-findings skill on the combined results from Step 3. Include any unresolved PR comments from Step 1 as additional findings for evaluation.

Step 5: Run /resolve-findings Skill

If zero actionable findings survive evaluation, report that the code looks clean and stop.

Otherwise, run the /resolve-findings skill on the accepted findings from Step 4.

Rules

  • If fetching PR comments fails, proceed with code review only.

How to use it

Copy the folder

Take tobihagemann/review-pr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.