address-pr-comments

Fetch and classify unresolved GitHub pull request comments by severity.

4|5|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fartybobo/farty-bobo --skill address-pr-comments-fartybobo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: address-pr-comments
Source: https://github.com/fartybobo/farty-bobo/tree/main/skills/address-pr-comments
Command: npx skills add https://github.com/fartybobo/farty-bobo --skill address-pr-comments-fartybobo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull request comments often accumulate across reviewers, leaving humans unsure which threads need action; this skill centralizes those human threads, separates them from bot noise, and drives a clear response plan.

Core Features & Use Cases

  • Human comment triage: fetches the active branch PR, distinguishes unresolved human feedback from automated bots, and tags severity levels to feed into an implementation plan.
  • Collaborative planning: presents the proposed changes, discussion flags, and ignored items to the human for selective approval before taking any action.
  • Execution with safety: runs /critique, resolves comment threads when possible, re-requests reviews, and checks CI status with gh pr checks, invoking resolve-ci-failures if needed.
  • Use case: For a feature PR with mixed nitpicks and architectural questions, use the skill to classify each comment, decide which edits to make now, and report back to reviewers after pushing.

Quick Start

Ask address-pr-comments to gather all unresolved GitHub PR comments, propose a plan by severity, and confirm each response before making code changes.

Frequently Asked Questions about address-pr-comments

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

FAQPage Schema
How do I resolve unresolved GitHub PR comments automatically?

To resolve GitHub PR comments, this skill fetches unresolved threads on the active branch, separates human feedback from bot noise, and proposes a severity-tagged plan for selective approval before pushing updates.

What is the best way to triage human feedback versus bot comments on a pull request?

Triage of human versus automated bot PR feedback is handled by fetching active branch comments, classifying the source, tagging severity levels, and presenting a collaborative implementation plan to the human reviewer.

How do I plan code changes based on GitHub PR review severity?

Planning code changes by PR review severity involves classifying unresolved human comments into severity tiers, then presenting proposed changes, discussion flags, and ignored items for human approval before any action is taken.

Does this PR comment resolution workflow check CI status before pushing updates?

Yes, the PR comment resolution workflow checks CI status using gh pr checks before pushing updates, and it invokes resolve-ci-failures if needed to ensure continuous integration passes after addressing feedback.

Can I selectively approve which GitHub PR comment threads get resolved?

You can selectively approve GitHub PR comment thread resolutions because the skill presents proposed changes, discussion flags, and ignored items to the human for confirmation before running /critique or taking action.