github-address-comments

Convert GitHub PR review threads into prioritized code-change plans.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill github-address-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-address-comments
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/github-address-comments
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill github-address-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Converts GitHub PR review threads into prioritized, traceable fixes with verifiable changes and closure evidence.

Core Features & Use Cases

  • Prioritizes unresolved review threads by severity and impact.
  • Generates focused code-change plans and reviewer-verifiable responses.
  • Provides templates and logs to support consistent, auditable workflows.

Quick Start

Run the skill against a target PR to fetch review threads and generate a prioritized resolution plan.

Frequently Asked Questions about github-address-comments

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

FAQPage Schema
How do I triage GitHub PR review comments into verifiable fixes?

To triage GitHub PR review comments, you map each unresolved thread to concrete, verifiable code changes. This process generates focused plans and reviewer-visible validation to ensure traceable closure evidence for every resolved comment.

What is the best way to prioritize unresolved GitHub PR review threads?

The best way to prioritize unresolved GitHub PR review threads is by evaluating severity and impact. This triage process converts review threads into prioritized resolution plans, ensuring high-impact issues are addressed first with auditable logs.

Can I automate GitHub PR comment triage to generate code-change plans?

Yes, you can automate GitHub PR comment triage to generate focused code-change plans. The skill fetches review threads and produces reviewer-verifiable responses, constraining actions strictly to repository code and comments for safety.

Does this PR comment triage approach work without modifying external systems?

Yes, this PR comment triage approach works safely by enforcing constraints that limit actions strictly to repository code and comments. It does not modify external systems, providing templates and logs to support consistent, auditable workflows.

How do I provide traceable closure evidence for resolved GitHub PR comments?

You provide traceable closure evidence for resolved GitHub PR comments by mapping each thread to verifiable code changes. This generates reviewer-visible validation and logs, ensuring the implementation follow-up is fully auditable.