mcpbeat Sign in

Reviewing Prs Agent Skill

General workflow for fetching, inspecting, reviewing GitHub Pull Requests using the gh CLI, drafting user-aligned review comments, and securing approval before posting. Use when asked to review a GitHub PR or pull request.

569 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1727
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/flutter/devtools --skill reviewing-prs

The instruction itself

7 sections, as written by the author

Reviewing Pull Requests

This skill outlines the workflow for inspecting GitHub Pull Requests using the gh CLI, drafting review feedback, and securing user approval before posting review comments.

Approval Safeguard (Strict Requirement)

> [!IMPORTANT]

> NEVER post comments or reviews to GitHub without explicit prior user approval.

> Always present draft review comments to the user in natural language first. Only execute write commands (gh pr comment, gh pr review) after the user approves.

Workflow

1. Request Information via GitHub CLI

  • PR Details:
  gh pr view <pr-number> --repo <owner/repo> --json title,body,author,state,headRefName,baseRefName,comments,reviews,files
  • Code Diff:
  gh pr diff <pr-number> --repo <owner/repo>
  • Existing Inline Comments:
  gh api repos/<owner/repo>/pulls/<pr-number>/comments
  • CI / Status Checks:
  gh pr checks <pr-number> --repo <owner/repo>

2. Inspect Context & Prior Feedback

  • Read the PR description, linked issues, and full diff.
  • Verify whether existing bot or human comments have already been addressed in subsequent commits.

3. Draft Review Comments

  • Keep comments direct, concise, and focused on code quality and correctness.
  • Approvals: Keep comments concise (LGTM or A couple comments but lgtm.). Avoid fluffy praise or re-summarizing the PR.
  • Actionable Feedback: Reference specific files, line numbers, and rationale when leaving suggestions.

4. Present Draft & Post Only Upon User Approval

> [!IMPORTANT]

> NEVER post comments or reviews to GitHub without explicit prior user approval.

  • Present the drafted review comments to the user in your response window.
  • Ask for confirmation: *"Would you like me to submit this review to GitHub?"*
  • Once explicitly approved by the user, post the review:
   gh pr review <pr-number> --repo <owner/repo> --comment --body "<approved review text>"

Other skills for the same job

different authors, same section of the catalogue
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens
Verification & Quality Assurance
by Microck
×2

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

4k tokens
Gh CLI
by christophacham
×2

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

10k tokens
Github
by Dicklesworthstone
×2

GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.

1k tokens
Codebase Cleanup Refactor Clean
by ComeOnOliver
×2

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

9k tokens
Codebase Cleanup Tech Debt
by ComeOnOliver
×2

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

6k tokens

How to use it

Copy the folder

Take flutter/reviewing-prs 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.