address-pr-comments

Triages open review threads on merge requests and pull requests, then implements, replies, and resolves each one.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working through a round of code review feedback by hand means reading every thread, deciding whether to fix or push back, writing tested fixes, and replying on each thread individually. This Skill automates that entire loop on GitLab merge requests and GitHub pull requests while keeping the human reviewer in control of disagreements. ## Core Features & Use Cases - Thread triage and classification: Reads every open review thread and classifies it as already fixed, needs fix, or disagree, then acts accordingly. - Tested, atomic fixes: Implements each agreed fix as its own commit with a failing test first, runs the full test suite, and pushes only to the source branch. - Host adapters for GitLab and GitHub: Ships adapter references covering authentication, thread listing, threaded replies, and thread resolution via glab and gh, with graceful degradation to other hosts through tool discovery. - Use Case: A reviewer leaves twelve comments on your GitHub PR. Invoke the command with the PR URL, and each thread gets a tested fix commit, an in-thread reply citing the commit SHA, and a resolution, while threads you disagree with get a reasoned reply and stay open. ## Quick Start Ask the AI to address all open review comments on your merge request or pull request by providing its URL, for example by invoking /address-pr-comments with the MR or PR link.

Frequently Asked Questions about address-pr-comments

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

FAQPage Schema
How do I address all review comments on a GitHub pull request automatically?▼

Invoke the command with the pull request URL. It lists every unresolved review thread via the GitHub GraphQL API, classifies each one, implements tested fixes as atomic commits, replies in-thread with the commit SHA, and resolves the thread.

How do I resolve GitLab merge request discussions from the command line?▼

The skill uses the glab API to list MR discussions, post threaded replies as notes, and resolve discussions with a PUT request. Resolving requires the Developer role or above on the project; on a 403 the reply still posts and the thread is flagged for manual resolution.

Does it work with GitHub and GitLab, or only one code host?▼

It ships with dedicated adapters for both GitLab and GitHub covering their specific APIs and CLI tooling. For any other host, it degrades gracefully by discovering available tools through ToolSearch and proceeds on a best-effort basis.

What happens when I disagree with a reviewer's comment?▼

Threads classified as disagree get a reasoned reply explaining the pushback and are left unresolved. Closing a thread raised by a reviewer is the reviewer's decision, so the skill never resolves a thread it disagrees with.

Why does the skill refuse to push or stop during workspace setup?▼

The setup script refuses when a leftover worktree is dirty, the clone has uncommitted changes or unpushed commits, or another worktree holds the source branch. It also never force-pushes and never pushes against a failing test suite.

Can it review my code and find new issues?▼

No. It only acts on threads that reviewers already raised and does not evaluate the change on its own merits. For a first-pass review that surfaces new findings, use a dedicated review skill such as /pr-review instead.