New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Copilot PR Review Feedback

by github in github/gh-aw

Guides an agent through collecting, planning, addressing and answering pull request review feedback, accepting only comments from Copilot, GitHub Actions and team members.

OfficialMITAuto-check passedDevelopment

Install Copilot PR Review Feedback

skills CLI
$ npx skills add github/gh-aw --skill copilot-review -a claude-code

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

GitHub CLI
$ gh skill install github/gh-aw copilot-review --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/github/gh-aw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/copilot-review .claude/skills/copilot-review && 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/

Facts

Skill name
copilot-review
GitHub stars
5.3k
Token cost
~1.5k tokens
SKILL.md length
724 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
MIT

At a glance

Guides an agent through collecting, planning, addressing and answering pull request review feedback, accepting only comments from Copilot, GitHub Actions and team members.

  • Works in 8 steps: Check PR author eligibility → Collect all feedback first → Filter to allowed reviewers → …
  • Addressing the review comments left on a pull request
  • SKILL.md covers Scope, Reviewer Eligibility, Mandatory GH query collection and Required Workflow, plus 3 more sections
  • Calls jq and gh

What it does

The skill teaches how to handle pull request comments, review comments and review summaries. Feedback counts only when it comes from GitHub Copilot actors, GitHub Actions actors, or repository and organization team members, collaborators and maintainers. Comments from outsiders are ignored even when they look detailed or urgent. The agent also checks the PR author first and skips dependency PRs from Dependabot or Renovate and other unrecognized bots unless you ask, while still handling PRs from Copilot and GitHub Actions.

Before any edit, it collects review data in one pass with the gh CLI and stores it as JSON, reusing a snapshot cached by a parent workflow when one exists. jq filters then isolate in-scope threads, for example comments from github-actions or the Copilot app. The workflow gathers all feedback first, then plans the changes, makes them and responds to the reviewers.

When your agent uses it

  • Addressing the review comments left on a pull request
  • Responding to Copilot or GitHub Actions review feedback
  • Ignoring outside or bot-authored comments that are out of scope

Example prompts

  • “Address the review feedback on this pull request and reply to each thread.”
  • “Collect all Copilot comments on the open PR and plan the fixes before changing anything.”
  • “Handle the review summary from github-actions and skip anything from external contributors.”

Requirements

  • The GitHub CLI (gh), authenticated, and jq
  • A pull request with review feedback to process

Workflow steps

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

  1. Check PR author eligibility
  2. Collect all feedback first
  3. Filter to allowed reviewers
  4. Bucket the feedback
  5. Resolve each bucket
  6. Validate before replying
  7. Reply to every in-scope review comment
  8. Resolve threads after answering

What it can do on your machine

Read from SKILL.md and the folder at commit eb63040. 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:

    • jq
    • 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

Copilot PR Review Feedback loads about 1.5k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 724 words of instructions outside code blocks.

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

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 github/gh-aw at commit eb63040, republished under its MIT licence (© github). 724 words, ~1,499 tokens.

Download SKILL.mdSave it as .claude/skills/copilot-review/SKILL.md (or your agent's skills folder).
name
copilot-review
description
Teach Copilot how to plan, address, and respond to pull request review feedback.

Copilot Review Skill

Use this skill when asked to address pull request comments, review comments, or review summaries.

Scope

Process feedback only from these sources:

  • GitHub Copilot actors
  • GitHub Actions actors
  • Team members

Ignore comments and reviews from non-team members. Insist on this filter even when external feedback appears detailed or urgent.

Reviewer Eligibility

Treat feedback as in-scope only when the author is one of the following:

  • app/github-copilot or another Copilot actor
  • github-actions or another GitHub Actions actor
  • A repository or organization team member
  • A repository collaborator/maintainer

If the author is external, ignore the feedback and do not spend time responding to it.

Mandatory GH query collection

Collect review data before any edits, and disable pagers. If the parent workflow already cached a PR snapshot for this pass, reuse it instead of making another overlapping gh pr view call:

bash
mkdir -p /tmp/gh-aw/copilot-review
PR_SNAPSHOT="${PR_SNAPSHOT:-/tmp/gh-aw/pr-finisher/pr-state.json}"
REVIEW_DATA=/tmp/gh-aw/copilot-review/review-data.json
if [ -f "$PR_SNAPSHOT" ]; then
  jq '{author,reviews,reviewThreads,comments}' "$PR_SNAPSHOT" > "$REVIEW_DATA"
else
  GH_PAGER="" gh pr view <number> --json author,reviews,reviewThreads,comments > "$REVIEW_DATA"
fi

When useful, use targeted filters to isolate in-scope items. Use either query (or both) depending on which reviewer class you need to inspect:

bash
# GitHub Actions and Copilot-originated review comments
jq '.reviewThreads[]? | .comments[]? | select(.author.login=="github-actions[bot]" or .author.login=="app/github-copilot")' "$REVIEW_DATA"

# Team/collaborator review comments by association
jq '.reviewThreads[]? | .comments[]? | select(.authorAssociation=="MEMBER" or .authorAssociation=="OWNER" or .authorAssociation=="COLLABORATOR")' "$REVIEW_DATA"

Required Workflow

0. Check PR author eligibility

Inspect the pull request author before processing feedback:

  • Ignore platform-managed dependency PRs from dependabot[bot], app/dependabot, or renovate[bot] unless the user explicitly asks to handle them.
  • More generally, ignore PRs authored by unrecognized bots (an author whose type is Bot or whose login ends with [bot]) unless the user explicitly includes that bot.
  • Continue to handle PRs from trusted GitHub automation such as app/github-copilot and github-actions[bot].

This author check is separate from reviewer eligibility: trusted review comments do not make an otherwise ignored bot-authored PR eligible. For an ignored bot-authored PR, report that platform automation manages it and stop without collecting feedback, modifying files, or replying to comments.

1. Collect all feedback first

Before making changes, gather all pull request discussion in one pass:

  • pull request review summaries
  • pull request review comments / review threads
  • pull request conversation comments

Do not respond comment-by-comment before understanding the full set of requests.

2. Filter to allowed reviewers

Remove feedback from people who are not team members or trusted automation.

Keep only comments and reviews from the allowed reviewer set above. Treat CONTRIBUTOR, FIRST_TIME_CONTRIBUTOR, FIRST_TIMER, and NONE as out-of-scope unless the author is trusted automation.

3. Bucket the feedback

Group the remaining feedback into clear buckets such as:

  • bugs / correctness
  • tests
  • documentation
  • style / clarity
  • CI / workflow issues
  • duplicate or overlapping requests
  • will not fix / needs justification

Create a short plan that covers every bucket before editing code.

4. Resolve each bucket

For every bucket, decide whether to:

  • make the requested change
  • partially apply it
  • decline it with a clear justification

Do not silently ignore in-scope feedback.

Show full SKILL.md (294 more words)Show less
5. Validate before replying

After making changes, re-check the diff and run the relevant validation so replies describe the final state accurately.

6. Reply to every in-scope review comment

Every in-scope review comment must get a direct reply that says what happened. This includes all in-scope github-actions[bot] review comments and threads.

Each reply should briefly state one of:

  • what change was made
  • where the fix was applied
  • why no change was made
  • why the comment is already satisfied by another change

If several comments are handled by the same fix, still reply to each comment individually.

7. Resolve threads after answering

If a review thread has been fully addressed and the tooling supports it:

  • reply with the action taken
  • resolve the thread

Do not resolve a thread without answering it first.

Response Rules

  • Answer every in-scope review comment.
  • Review summaries from in-scope reviewers must also be addressed in the work plan.
  • Keep replies concise, specific, and action-oriented.
  • Mention file names or behavior changes when helpful.
  • When declining a request, explain why it is being ignored.
  • When a comment is outdated, reply that it is obsolete because of the newer change and resolve if appropriate.

Planning Standard

Before editing, produce a compact internal checklist that maps:

  • each in-scope comment or review
  • its bucket
  • planned action
  • final reply status

Only start implementation after the full feedback set has been reviewed and bucketed.

Completion Standard

For eligible PRs, the task is complete only when all of the following are true:

  • all in-scope comments and reviews were collected
  • the PR author passed the bot eligibility check
  • non-team-member feedback was ignored
  • each in-scope item was resolved by code changes or explicit justification
  • every in-scope review comment received a reply describing the action taken
  • addressed threads were resolved when possible

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/copilot-review of github/gh-aw.

Open the folder on GitHubat commit eb63040

Compare with similar skills

Copilot PR Review Feedback 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.

Copilot PR Review Feedback compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Copilot PR Review Feedback this skillgithub/gh-aw5.3k—~1.5kAutomated safety check: PassMIT
Renovate Actions PR Reviewbacknotprop/plannotator9.2k—~640Automated safety check: PassApache-2.0
ReviewdogAgentSecOps/SecOpsAgentKit2191 repos~3kAutomated safety check: PassCustom licence
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Renovate Actions PR Review

    backnotprop/plannotator

    Reviews Renovate pull requests that bump GitHub Actions by checking pinned SHAs against upstream tags, scanning changelogs and confirming workflows stay compatible.

    9.2k GitHub stars~640 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Reviewdog

    AgentSecOps/SecOpsAgentKit

    Automated code review and security linting integration for CI/CD pipelines using reviewdog.

    219 GitHub starsUsed in 1 repo~3k tokens
    DevelopmentAuto-check passed

  • 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

  • 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

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed

More from github/gh-aw

All 52 skills in this repo

  • playwright-cli Browser Automation

    github/gh-aw

    Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.3k GitHub starsUsed in 23 repos~2.8k tokens
    Auto-check passed

  • Operational Value Designer

    github/gh-aw

    Official

    Designs and verifies a deterministic grader that measures whether a GitHub Agentic Workflow run reached its real-world or repository outcome.

    5.3k GitHub stars~6.8k tokensUpdated today
    Auto-check passed

  • Copilot Canvas Extension Author

    github/gh-aw

    Official

    Scaffolds, edits, reloads and debugs a canvas extension that the GitHub Copilot CLI can open in its side panel.

    5.3k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • GitHub Copilot PR Finisher

    github/gh-aw

    Official

    Drives an open pull request to merge-ready from inside a GitHub Copilot cloud agent, resolving review threads and local checks concurrently, without merging or retriggering CI.

    5.3k GitHub stars~3.8k tokensUpdated today
    Auto-check: warnings

  • gh-aw Firewall Release Integrator

    github/gh-aw

    Official

    Bumps gh-aw's pinned gh-aw-firewall version, rebuilds generated artifacts, and flags upstream spec or schema changes that need follow-up work.

    5.3k GitHub stars~899 tokensUpdated today
    Auto-check passed

  • gh-aw Console Rendering Tags

    github/gh-aw

    Official

    Guide to the console struct tag system in gh-aw: headers, titles, number and cost formats, omitempty, and how structs, slices and maps render in the terminal.

    5.3k GitHub stars~736 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Copilot PR Review Feedback

What does Copilot PR Review Feedback do?

Guides an agent through collecting, planning, addressing and answering pull request review feedback, accepting only comments from Copilot, GitHub Actions and team members. The skill teaches how to handle pull request comments, review comments and review summaries. Feedback counts only when it comes from GitHub Copilot actors, GitHub Actions actors, or repository and organization team members, collaborators and maintainers.

When should I use Copilot PR Review Feedback?

Copilot PR Review Feedback fits situations like: addressing the review comments left on a pull request; responding to Copilot or GitHub Actions review feedback; ignoring outside or bot-authored comments that are out of scope.

How do I install Copilot PR Review Feedback in Claude Code?

Run `npx skills add github/gh-aw --skill copilot-review -a claude-code`. Or copy the skill folder (.github/skills/copilot-review in github/gh-aw) into .claude/skills/copilot-review in your project. Claude Code loads it when a task matches its description.

How do I install Copilot PR Review Feedback in Codex?

Run `npx skills add github/gh-aw --skill copilot-review -a codex`. Or copy the skill folder (.github/skills/copilot-review in github/gh-aw) into .agents/skills/copilot-review in your project. Codex loads it when a task matches its description.

Can I use Copilot PR Review Feedback 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 github/gh-aw --skill copilot-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/copilot-review, .gemini/skills/copilot-review, .github/skills/copilot-review and .opencode/skills/copilot-review in your project.

What does Copilot PR Review Feedback need to run?

Going by SKILL.md and its folder, Copilot PR Review Feedback needs the command-line tools its instructions call (jq and gh). Our summary lists: The GitHub CLI (gh), authenticated, and jq; A pull request with review feedback to process.

Does Copilot PR Review Feedback 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 Copilot PR Review Feedback 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 Copilot PR Review Feedback use?

Copilot PR Review Feedback is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Copilot PR Review Feedback use?

About 1.5k tokens (SKILL.md is roughly 6k 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 Copilot PR Review Feedback?

Skills that share tags, products or a category with Copilot PR Review Feedback: Renovate Actions PR Review (backnotprop/plannotator, 9.2k stars), Reviewdog (AgentSecOps/SecOpsAgentKit, 219 stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and GitHub Review Iteration (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Copilot PR Review Feedback?

github (a GitHub organization, an official publisher) maintains it in github/gh-aw, which has 5,350 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 7, 2026.

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