pr-address

Automate PR review comment fixes and CI green workflows across GraphQL and REST.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ghpworkuse-web/train --skill pr-address
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-address
Source: https://github.com/ghpworkuse-web/train/tree/main/AutoGPT/.claude/skills/pr-address
Command: npx skills add https://github.com/ghpworkuse-web/train --skill pr-address

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Addresses PR review feedback and coordinates fixes to drive CI green, reducing manual back-and-forth and ensuring alignment between code changes and reviews.

Core Features & Use Cases

  • End-to-end PR feedback loop: fetch unresolved inline review threads, top-level reviews, and PR conversations across GraphQL and REST, with full pagination to cover all cycles.
  • Automated fix and reply workflow: create commits, push changes, and post inline replies referencing the commit with a link, ensuring reviewers see the exact patch.
  • Thread resolution and CI tracking: resolve threads only after concrete fixes, monitor CI status, and continue addressing new comments until all checks pass.

Quick Start

Retrieve the target PR, collect all unresolved threads across GraphQL and REST, fix the issues, commit and push, post inline replies with the commit link, and resolve every thread.

Frequently Asked Questions about pr-address

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

FAQPage Schema
How do I automate addressing PR review comments until CI is green?

Automating PR review feedback involves fetching unresolved threads, committing fixes, pushing changes, posting inline replies, and monitoring CI status until all checks pass. This workflow iterates across multiple review cycles to align code with feedback.

What is the best way to reply to inline GitHub PR reviews with commit references?

Replying to inline GitHub PR reviews with commit references requires fetching unresolved threads via GraphQL and REST, creating a commit, and posting an inline reply containing a link to that specific patch so reviewers can verify the fix.

How does an automated PR workflow handle pagination and unresolved conversations?

Automated PR workflows handle pagination by fetching all unresolved inline review threads, top-level reviews, and PR conversations across GraphQL and REST sources, ensuring no feedback is missed during the iterative fixing process.

Can I automatically resolve GitHub PR threads after pushing fixes?

Yes, you can automatically resolve GitHub PR threads after pushing concrete fixes. The workflow creates commits, pushes changes, posts inline replies with commit links, and resolves threads while respecting rate limits and potential merge conflicts.

What happens if merge conflicts occur during automated PR feedback resolution?

When merge conflicts occur during automated PR feedback resolution, the workflow respects these conflicts as a constraint. It manages rate limits and thread resolution carefully, only resolving conversations after concrete fixes are successfully committed and pushed.