Menu

Individual skill

pr-address-feedback

Walk through PR review comments one-by-one, deciding for each whether to act on the feedback or reply with reasoning, and build an approvable resolution plan before changing anything. Use when the user wants to address, respond to, or triage PR review feedback.

skills/pr-address-feedback/SKILL.md

Read pinned source

Source commit edbecfa9099c4addae1f500cca1ac067204b30fd

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40,901
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Let's look at each review comment on this pull request one-by-one and make a plan to either take action on the feedback or reply with reasoning.

PR target: use the PR number/URL I passed with this command, if any; otherwise the PR for the current branch.

You are in **plan mode**. Until I approve the final plan, do NOT edit files, commit, push, resolve threads, or post anything to GitHub. Read-only commands (`gh`, `git log/diff/show`, viewing files) are fine.

The PR may live on github.com or on another GitHub host (e.g. GitHub Enterprise Server). Take the host from the PR's `url` and pass `--hostname <host>` to every `gh api` call (or `export GH_HOST=<host>` once). `gh api` defaults to github.com even inside an Enterprise Server checkout.

## 1. Gather the feedback

- Resolve the PR: use the target above if provided (number, URL, or `owner/repo#N`); otherwise use the PR for the current branch (`gh pr view --json number,url,headRefName,headRefOid,baseRefName,headRepository,headRepositoryOwner`). If none is found, ask me.
- Fetch **all** review threads with GraphQL (paginate), including for each thread: `id`, `isResolved`, `isOutdated`, `path`, `line`, `startLine`, `originalLine`, `diffSide`, and every comment's `databaseId`, `url`, `author.login`, `body`, `diffHunk`, `createdAt`.
- Also fetch top-level review bodies (`reviews` with non-empty `body`) and general PR conversation comments, since those can contain feedback too.
- Skip resolved threads and threads where I (the PR author) had the last word unless they still look unaddressed. Mention outdated threads but check whether the feedback still applies to current code.