pr-review

Automate PR code reviews via GitHub MCP Server with inline comments.

1|Updated Oct 13, 2022
One-click install
npx skills add https://github.com/kryota-dev/dotfiles --skill pr-review-kryota-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/kryota-dev/dotfiles/tree/main/.bin/.claude/skills/pr-review
Command: npx skills add https://github.com/kryota-dev/dotfiles --skill pr-review-kryota-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates code reviews for Pull Requests by leveraging a GitHub MCP Server to retrieve PR details and reflect review results.

Core Features & Use Cases

  • Initiate reviews: start a pending PR review with MCP commands.
  • Diff analysis: fetch diffs and line changes to understand modifications.
  • Inline feedback: add targeted review comments and attach suggestions.
  • Review submission: submit reviews with the appropriate event type (COMMENT) and summarize findings.

Quick Start

Start a review by creating a pending PR review, inspect the diff, and proceed with inline comments and final submission.

Frequently Asked Questions about pr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request code reviews on GitHub?

Automated pull request code reviews interface with a GitHub MCP Server to fetch PR data, inspect diffs, add inline comments, and submit structured feedback as a final comment.

What is the process for adding inline comments to a GitHub PR using an MCP server?

Adding inline comments requires starting a pending PR review via MCP commands, analyzing the fetched line diffs, attaching targeted suggestions to specific lines, and submitting the review as a comment.

Do I need a linked MCP server workflow to run automated GitHub code reviews?

Yes, automated GitHub code reviews require an active Pull Request in a GitHub repository and a linked MCP server workflow to retrieve PR details and reflect review outcomes.

Can I fetch PR diffs and analyze line changes through a GitHub MCP Server?

Yes, you can fetch PR diffs and line modifications through a GitHub MCP Server to understand code changes before attaching targeted review comments and submitting the final review.

What are the limitations of using MCP commands for PR code review submission?

MCP commands for PR code review submission are limited to reflecting outcomes as a COMMENT event type, targeting GitHub repositories with active PRs and linked MCP server workflows.