skills.rest
furkankoykiran
furkankoykiranCOMMUNITY
Explore all skills by this author →
Website𝕏@furkankoykiranGitHub

pr-followup

Fetch GitHub pull request context and prioritize review feedback.

4|1|Updated Apr 26, 2026
Search Tags:#github#code-review#pull-request#review-feedback#ci-status#change-requests#pr-followup
One-click install
npx skills add https://github.com/furkankoykiran/.claude --skill pr-followup-furkankoykiran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-followup
Source: https://github.com/furkankoykiran/.claude/tree/main/skills/pr-followup
Command: npx skills add https://github.com/furkankoykiran/.claude --skill pr-followup-furkankoykiran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking and responding to GitHub pull request review comments, change requests, and follow-up feedback across long, multi-participant discussion threads is time-consuming and error-prone, often leading to missed requests, delayed PR merges, and miscommunication with reviewers.

Core Features & Use Cases

  • Full PR Context Aggregation: Automatically pulls all review comments, inline code threads, general issue discussions, CI check statuses, and file diffs for any target GitHub pull request.
  • Timeline Reconstruction: Builds a chronological record of all PR activity to isolate new feedback received after your last commit or comment, so you never miss updates from reviewers or automated bots.
  • Actionable Feedback Prioritization: Reasons through reviewer intent to group related requests, prioritize blocking issues first, and distinguish between changes you can implement now and input you are waiting on from other contributors.
  • Use Case: If you submitted a PR that received 3 new change requests, a failing CI check, and a clarification question from a reviewer after your last update, this skill will map out exactly what needs to be fixed, what needs a reply, and what is waiting on external input, then guide you through executing the required steps after your approval.

Quick Start

Use the pr-followup skill to address all pending review feedback and requested changes for the pull request at https://github.com/microsoft/playwright/pull/39401.

Frequently Asked Questions about pr-followup

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

FAQPage Schema
How do I track and respond to GitHub pull request review feedback across multiple threads?▼

To track GitHub pull request review feedback, you can aggregate all inline code comments, CI statuses, and change history into a single chronological timeline. This reconstructs PR activity to isolate new feedback received after your last commit, preventing missed change requests.

How do I prioritize blocking change requests and failing CI checks on an open pull request?▼

Prioritize blocking change requests by reasoning through reviewer intent to group related feedback, distinguish blocking issues from clarification questions, and separate actionable fixes from input waiting on other contributors.

What is the best way to manage long multi-participant PR discussion threads to avoid missing updates?▼

Managing long PR discussion threads requires building a chronological record of all activity to isolate new feedback from reviewers or automated bots after your last update. This timeline reconstruction ensures you catch every change request and failing CI check.

Can I use this to distinguish between reviewer change requests I can implement now and input I am waiting on?▼

Yes, you can distinguish between actionable change requests and pending external input. The skill analyzes reviewer intent to group related requests, prioritizes blocking issues, and maps out exactly what needs a reply versus what is waiting on other contributors.

How do I address pending PR review feedback and execute requested fixes step by step?▼

To address pending PR review feedback, fetch the full PR context including inline comments and file diffs, prioritize actionable feedback, and guide the implementation of requested fixes and formal reviewer responses step by step after your approval.

Why does manually tracking GitHub PR review comments lead to delayed merges?▼

Manually tracking GitHub PR review comments leads to delayed merges because extended multi-participant discussion threads are error-prone, often resulting in missed change requests and miscommunication with reviewers that block progress toward merging.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

collect-pr-feedback

Collect and consolidate GitHub pull request feedback and CI check statuses.

Official
Intermediate
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
kriscendobotkriscendobot
3

pr-ci-watch

Monitor GitHub pull request CI status check transitions and terminal states.

Community
Advanced
strawgatestrawgate

resolve-pr-threads

Audit, resolve, and unresolve GitHub pull request comment threads via GraphQL API.

Community
Intermediate