pr-review-resolver

Triage GitHub pull request review comments using Linear ticket context.

4|2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/stepandel/clawup --skill pr-review-resolver-stepandel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-resolver
Source: https://github.com/stepandel/clawup/tree/main/examples/multi-agent/eng/skills/pr-review-resolver
Command: npx skills add https://github.com/stepandel/clawup --skill pr-review-resolver-stepandel

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of addressing feedback on GitHub pull requests, ensuring that all review comments are systematically handled, saving developers time and improving code quality.

Core Features & Use Cases

  • Comment Triage: Classifies each review comment into 'resolve-as-suggested', 'resolve-differently', or 'ignore'.
  • Contextual Decision Making: Leverages project context from Linear tickets to make informed decisions about comment resolution.
  • Automated Changes: Applies suggested code changes or implements alternative solutions.
  • Use Case: After receiving feedback on a pull request, use this Skill to automatically go through each comment, decide whether to implement the suggestion, offer an alternative, or explain why it's being ignored, and then push the changes.

Quick Start

Use the pr-review-resolver skill to address all comments on pull request number 123.

Frequently Asked Questions about pr-review-resolver

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

FAQPage Schema
How do I automate resolving GitHub pull request review comments?

Automating GitHub pull request review comments involves triaging each comment to resolve-as-suggested, resolve-differently, or ignore, and then applying code changes automatically. This Skill uses project context from Linear tickets to make informed resolution decisions and provides a summary table of actions taken.

Do I need the gh CLI to automate pull request code review feedback?

Yes, automating pull request code review feedback requires the gh CLI and GitHub API access to fetch PR details and comments. These tools provide the necessary interface to retrieve review data and apply automated code changes based on triage decisions.

Can I use Linear ticket context to inform pull request comment triage decisions?

Yes, you can use Linear ticket context to inform pull request comment triage decisions. The Skill leverages project context from Linear tickets to decide whether to implement a reviewer's suggestion, offer an alternative solution, or ignore the comment entirely.

What is the best way to systematically address multiple GitHub PR comments?

The best way to systematically address GitHub PR comments is to classify each one into resolve-as-suggested, resolve-differently, or ignore, and then automate the code changes based on those decisions. This ensures all feedback is handled efficiently without missing any comments.

How does automated PR comment triage handle comments it decides to ignore?

Automated PR comment triage handles ignored comments by bypassing code changes for them while documenting the decision in a summary table. The Skill explains why a comment is being ignored based on the project context gathered from Linear tickets.