How do I install the Reviewing Prs skill?

Run npx skillmds@latest add flutter/reviewing-prs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Reviewing Prs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Reviewing Prs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Reviewing Prs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Reviewing Prs?

flutter (@flutter) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Reviewing Prs by flutter — Agent Skill

Name: Reviewing Prs
Author: flutter

Reviewing Prs

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.

flutter 10da0d1 2.2 KB Updated Sep 17, 2026

File contents

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>"

---name: reviewing-prsdescription: 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.---# Reviewing Pull RequestsThis 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**: ```bash gh pr view <pr-number> --repo <owner/repo> --json title,body,author,state,headRefName,baseRefName,comments,reviews,files ```- **Code Diff**: ```bash gh pr diff <pr-number> --repo <owner/repo> ```- **Existing Inline Comments**: ```bash gh api repos/<owner/repo>/pulls/<pr-number>/comments ```- **CI / Status Checks**: ```bash 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.**1. Present the drafted review comments to the user in your response window.2. Ask for confirmation: *"Would you like me to submit this review to GitHub?"*3. Once explicitly approved by the user, post the review: ```bash gh pr review <pr-number> --repo <owner/repo> --comment --body "<approved review text>" ```

Frequently asked questions