address-pr-comments

Fetch unresolved GitHub review threads and implement fixes via multi-agent worktrees.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/erichugy/agentic.skills --skill address-pr-comments-erichugy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: address-pr-comments
Source: https://github.com/erichugy/agentic.skills/tree/main/address-pr-comments
Command: npx skills add https://github.com/erichugy/agentic.skills --skill address-pr-comments-erichugy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many pull requests accumulate unresolved review threads that require manual triage, implementation, security checks, and style fixes; this Skill orchestrates those steps so maintainers and contributors can close review loops faster and with higher confidence.

Core Features & Use Cases

  • Automated Triage: Fetches unresolved review threads, classifies them as actionable, acknowledged, or noise, and presents a grouped triage for user approval.
  • Multi-Agent Implementation: Orchestrates researcher, implementer, security reviewer, and style enforcer subagents using isolated git worktrees to implement fixes, run builds, and enforce coding conventions.
  • No-Op Detection & Safety: Verifies requested changes are not no-ops, runs linters/builds, applies security checklists, and prevents committing purely cosmetic or redundant changes.
  • Thread Resolution & Reporting: Resolves threads via GitHub GraphQL after fixes, replies to acknowledged comments, and produces a structured report including security and style findings.
  • Use Cases: Single-PR fixes, batch processing across multiple PRs, and continuous improvement proposals based on recurring review patterns.

Quick Start

Address all open review comments on PR #42, implement fixes, run security and style reviews, and resolve the threads.

Frequently Asked Questions about address-pr-comments

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

FAQPage Schema
How do I automate resolving GitHub PR review comments?

Automate resolving GitHub PR review comments by fetching unresolved threads via gh and GraphQL, orchestrating multi-agent worktrees to implement fixes, running linters/builds, and pushing commits to close review loops faster.

What is the best way to triage and fix multiple pull request review threads?

Triage and fix multiple pull request review threads by classifying open comments as actionable, acknowledged, or noise, then using multi-agent implementation in isolated git worktrees to apply required code changes and security checks in batch workflows.

Can I use multi-agent worktrees to implement security and style fixes for code review?

Use multi-agent worktrees to implement security and style fixes by orchestrating researcher, implementer, security reviewer, and style enforcer subagents that run builds, apply security checklists, and enforce coding conventions before pushing commits.

How does no-op detection work when automating pull request comment resolution?

No-op detection works by verifying requested changes are not purely cosmetic or redundant, running linters and builds, and preventing the commit of no-op changes before resolving GitHub review threads via GraphQL.

Does automated PR review resolution work for batch processing across multiple pull requests?

Automated PR review resolution works for batch processing across multiple pull requests by fetching unresolved review threads, applying multi-agent implementation, and producing structured reports with security and style findings for each PR.

What are the limitations of automating GitHub PR thread resolution?

Limitations include relying on gh and GraphQL for fetching unresolved threads, requiring isolated git worktrees for multi-agent orchestration, and needing user approval for triage grouping before implementing fixes and resolving threads.