pr-feedback

Addresses GitHub PR review comments with one commit per item and resolves review threads.

Updated Oct 16, 2025
One-click install
npx skills add https://github.com/jlui17/dotfiles --skill pr-feedback-jlui17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-feedback
Source: https://github.com/jlui17/dotfiles/tree/main/agents/skills/pr-feedback
Command: npx skills add https://github.com/jlui17/dotfiles --skill pr-feedback-jlui17

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Review feedback on a pull request often stalls merges because threads stay open, fixes lack structure, and reviewer objections reveal undocumented reasoning. This Skill turns each review comment into a tracked, committed fix and closes resolved threads so the PR can merge. ## Core Features & Use Cases - One commit per feedback item: Each review comment gets its own commit, keeping the fix history clean and reviewable. - Documentation-gap handling: When an objection stems from missing context, the reasoning is captured in code, tests, or package docs rather than only in the PR thread. - Thread resolution via GraphQL: The bundled script lists unresolved review threads on a GitHub PR and resolves them by ID, since the gh CLI has no native subcommand for this. - Use Case: A reviewer leaves five comments on your PR. You address each in its own commit, reply with evidence where no change is needed, then run the script to list and resolve the addressed threads before merging. ## Quick Start Address each review comment on my open GitHub PR with one commit per item, then list and resolve the threads that are fixed.

Frequently Asked Questions about pr-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve a GitHub PR review thread from the command line?▼

GitHub's gh CLI has no subcommand for review threads, so resolution goes through the GraphQL API. The included script runs a resolveReviewThread mutation with the thread ID and confirms the resolved state.

How do I list unresolved review threads on a GitHub pull request?▼

Run the script with the list subcommand, passing the owner/repo and PR number. It queries the GraphQL reviewThreads endpoint and prints each unresolved thread's ID, file path, line, author, and first comment line.

How should I respond to PR review comments before merging?▼

Make one commit per feedback item, reply with evidence when no change is needed, then resolve the thread. Leave threads open only when the disposition needs the reviewer's judgment, such as an unaccepted pushback.

When should review feedback become documentation instead of a code change?▼

When an objection only holds because the reviewer lacks context you already had, the gap is documentation. Encode the reasoning in code or a test first, then package docs, reserving PR comments for information true only during the PR's lifetime.

Does the gh CLI support resolving review threads natively?▼

No, gh has no built-in subcommand for review threads. Both listing and resolving must go through gh api graphql with the reviewThreads query and resolveReviewThread mutation.