Agent skill

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.

BSD-3-ClauseAuto-check passedDevelopment

Install Reviewing PRs

skills CLI

$ npx skills add flutter/devtools --skill reviewing-prs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install flutter/devtools reviewing-prs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/reviewing-prs .claude/skills/reviewing-prs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "reviewing-prs" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/reviewing-prs into .claude/skills/reviewing-prs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-prs", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/flutter/devtools/tree/master/.agents/skills/reviewing-prs

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add flutter/devtools --skill reviewing-prs -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flutter/devtools reviewing-prs --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/reviewing-prs .agents/skills/reviewing-prs && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "reviewing-prs" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/reviewing-prs into .agents/skills/reviewing-prs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-prs", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flutter/devtools --skill reviewing-prs -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flutter/devtools reviewing-prs --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/reviewing-prs .cursor/skills/reviewing-prs && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "reviewing-prs" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/reviewing-prs into .cursor/skills/reviewing-prs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-prs", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/flutter/devtools.git --path .agents/skills/reviewing-prs

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flutter/devtools --skill reviewing-prs -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flutter/devtools reviewing-prs --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/reviewing-prs .gemini/skills/reviewing-prs && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "reviewing-prs" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/reviewing-prs into .gemini/skills/reviewing-prs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-prs", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install flutter/devtools reviewing-prs

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add flutter/devtools --skill reviewing-prs -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/reviewing-prs .github/skills/reviewing-prs && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "reviewing-prs" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/reviewing-prs into .github/skills/reviewing-prs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-prs", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flutter/devtools --skill reviewing-prs -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flutter/devtools reviewing-prs --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flutter/devtools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/reviewing-prs .opencode/skills/reviewing-prs && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "reviewing-prs" agent skill from https://github.com/flutter/devtools/tree/master/.agents/skills/reviewing-prs into .opencode/skills/reviewing-prs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reviewing-prs", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: reviewing-prs
GitHub stars: 1.7k
Token cost: ~570 tokens
SKILL.md length: 219 words
Files: 1
Skills in repo: 10
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: BSD-3-Clause

At a glance

General workflow for fetching, inspecting, reviewing GitHub Pull Requests using the gh CLI, drafting user-aligned review comments, and securing approval before posting.

Works in 4 steps: Request Information via GitHub CLI → Inspect Context & Prior Feedback → Draft Review Comments → …
Asked to review a GitHub PR
SKILL.md covers Approval Safeguard (Strict… and Workflow
Calls gh

What it does

Reviewing PRs is an agent skill from flutter/devtools. 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.

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: Developer tools for Flutter & Dart. The licence is BSD-3-Clause.

When your agent uses it

Asked to review a GitHub PR
Tasks that involve Pull requests

Example prompts

“/reviewing-prs”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Request Information via GitHub CLI
Inspect Context & Prior Feedback
Draft Review Comments
Present Draft & Post Only Upon User Approval

What it can do on your machine

Read from SKILL.md and the folder at commit 3a3b64a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Reviewing PRs loads about 570 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 219 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~570

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from flutter/devtools at commit 3a3b64a, republished under its BSD-3-Clause licence (© flutter). 219 words, ~570 tokens.

Download SKILL.mdSave it as .claude/skills/reviewing-prs/SKILL.md (or your agent's skills folder).

name: reviewing-prs
description: 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 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:

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.

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:

bash

gh pr review <pr-number> --repo <owner/repo> --comment --body "<approved review text>"

Files

Just SKILL.md in .agents/skills/reviewing-prs of flutter/devtools.

Open the folder on GitHubat commit 3a3b64a

Compare with similar skills

Reviewing PRs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Reviewing PRs compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Reviewing PRs this skillflutter/devtools	1.7k	—	~570	Automated safety check: Pass	BSD-3-Clause	today
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	yesterday
Check PRonyx-dot-app/onyx	32k	2 repos	~2.3k	Automated safety check: Pass	MIT	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
32k GitHub starsUsed in 2 repos~2.3k tokens
DevelopmentAuto-check passed
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
69k GitHub starsUsed in 2 repos~1.1k tokens
DevelopmentAuto-check passed
GitHub Review Iteration
prisma/orm
Official
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
48k GitHub stars~2.2k tokensUpdated today
DevelopmentAuto-check passed

More from flutter/devtools

All 10 skills in this repo

Adding Release Notes
flutter/devtools
Adds user-facing change descriptions to DevTools release notes.
1.7k GitHub stars~1k tokensUpdated today
Auto-check passed
Adding Copyright Headers
flutter/devtools
Adds copyright headers to files based on file type. An agent skill from flutter/devtools.
1.7k GitHub stars~640 tokensUpdated today
Auto-check passed
Debugging Devtools Extensions
flutter/devtools
Guidelines and step-by-step workflow for debugging DevTools extensions locally, including stub mode, fixed-port launching, browser auto-opening, URL query parameters, target app connection, and…
1.7k GitHub stars~839 tokensUpdated today
Auto-check passed
Closing Obsolete Issues
flutter/devtools
Find and close obsolete, stale, or not reproducible issues in the flutter/devtools repository.
1.7k GitHub stars~949 tokensUpdated today
Auto-check passed
Reviewing Devtools PRs
flutter/devtools
DevTools repository-specific PR review workflow enforcing DevTools style guidelines and common review patterns.
1.7k GitHub stars~638 tokensUpdated today
Auto-check passed
Adding Changelog Entries
flutter/devtools
A skill your agent uses when documenting changes in CHANGELOG.md files for devtoolsshared, devtoolsappshared, or devtoolsextensions.
1.7k GitHub stars~482 tokensUpdated today
Auto-check passed

Works with

GitHub

Questions about Reviewing PRs

What does Reviewing PRs do?

General workflow for fetching, inspecting, reviewing GitHub Pull Requests using the gh CLI, drafting user-aligned review comments, and securing approval before posting. Reviewing PRs is an agent skill from flutter/devtools. General workflow for fetching, inspecting, reviewing GitHub Pull Requests using the gh CLI, drafting user-aligned review comments, and securing approval before posting.

When should I use Reviewing PRs?

Reviewing PRs fits situations like: asked to review a GitHub PR; tasks that involve Pull requests.

How do I install Reviewing PRs in Claude Code?

Run `npx skills add flutter/devtools --skill reviewing-prs -a claude-code`. Or copy the skill folder (.agents/skills/reviewing-prs in flutter/devtools) into .claude/skills/reviewing-prs in your project. Claude Code loads it when a task matches its description.

How do I install Reviewing PRs in Codex?

Run `npx skills add flutter/devtools --skill reviewing-prs -a codex`. Or copy the skill folder (.agents/skills/reviewing-prs in flutter/devtools) into .agents/skills/reviewing-prs in your project. Codex loads it when a task matches its description.

Can I use Reviewing PRs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flutter/devtools --skill reviewing-prs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reviewing-prs, .gemini/skills/reviewing-prs, .github/skills/reviewing-prs and .opencode/skills/reviewing-prs in your project.

What does Reviewing PRs need to run?

Going by SKILL.md and its folder, Reviewing PRs needs the command-line tools its instructions call (gh).

Does Reviewing PRs access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Reviewing PRs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Reviewing PRs use?

Reviewing PRs is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Reviewing PRs use?

About 570 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Reviewing PRs?

Skills that share tags, products or a category with Reviewing PRs: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reviewing PRs?

flutter (a GitHub organization) maintains it in flutter/devtools, which has 1,732 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

Source: flutter/devtools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Reviewing PRs

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Reviewing Pull Requests

Approval Safeguard (Strict Requirement)

Workflow

1. Request Information via GitHub CLI

2. Inspect Context & Prior Feedback

3. Draft Review Comments

4. Present Draft & Post Only Upon User Approval

Files

Compare with similar skills

Similar skills

More from flutter/devtools

Related

Questions about Reviewing PRs