maiconfz--github-pr-review-triage--github-pr-review-triage

Triages GitHub pull request review feedback and resolves threads via gh CLI.

3|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/agents-repo/registry --skill maiconfz-github-pr-review-triage-github-pr-review-triage-agents-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maiconfz--github-pr-review-triage--github-pr-review-triage
Source: https://github.com/agents-repo/registry/tree/main/.cursor/skills/maiconfz/github-pr-review-triage/maiconfz--github-pr-review-triage--github-pr-review-triage
Command: npx skills add https://github.com/agents-repo/registry --skill maiconfz-github-pr-review-triage-github-pr-review-triage-agents-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Addressing pull request review feedback from Copilot and inline reviewers involves repetitive manual work: fetching unresolved threads, applying fixes, replying to each comment, and resolving threads one by one. This Skill automates that entire loop using the GitHub CLI. ## Core Features & Use Cases - Automated feedback fetching: Retrieves unresolved review threads via GraphQL and head-scoped Copilot review summaries with zero inline comments, with pagination and idempotency checks. - Structured triage and fixing: Classifies each item as needs_fix, fixed_remote, wont_fix, by_design, duplicate, or acknowledged before applying minimal scoped code changes. - Mandatory ship-mode closure: Validates changes with project checks, commits and pushes the PR head branch, then replies to and resolves every thread and acknowledges each Copilot summary. - Use Case: After Copilot leaves 8 inline comments and one summary review on your PR, invoke this Skill to fix the code, push the commit, reply to each thread, resolve them, and acknowledge the summary in one pass. ## Quick Start Ask the agent to triage and resolve all unresolved review feedback on pull request number 42 in the current repository.

Frequently Asked Questions about maiconfz--github-pr-review-triage--github-pr-review-triage

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

FAQPage Schema
How do I resolve Copilot review comments on a GitHub pull request automatically?▼

Use the gh CLI to fetch unresolved review threads via GraphQL, apply fixes, push the commit, then reply with addPullRequestReviewThreadReply and close each thread with resolveReviewThread. This Skill automates that full sequence.

How to fetch unresolved PR review threads with the GitHub CLI?▼

Run gh api graphql with a reviewThreads query filtered by isResolved == false, paginating with pageInfo.endCursor. Omit the after parameter on the first page since GitHub rejects an empty cursor.

Can Copilot review summaries be resolved like inline threads?▼

No. Copilot review summaries with zero inline comments have no resolve API. They are acknowledged by posting a PR conversation comment via gh pr comment referencing the review databaseId.

Does this workflow support dry-run mode without committing?▼

Yes. Setting dry-run to true fetches, triages, fixes, and validates only. Commit, push, reply, resolve, and acknowledge steps are skipped; the default false enables full ship-mode automation.

Why must reply bodies be written to a file before posting?▼

GitHub-sourced review text can break shell quoting or inject commands if interpolated into --body strings. Writing bodies to a file and passing them with --body-file or jq --rawfile prevents shell injection.