pr-review-triage

Triage pull request CI results and review comments into apply, defer, or skip dispositions.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill pr-review-triage-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-triage
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/pr-review-triage
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill pr-review-triage-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a pull request is opened, CI checks report and reviewers comment, but nothing tells you when to come back or what to do with each finding. This Skill reads everything the PR came back with and gives every check result and review comment an explicit disposition, so nothing is silently ignored or left floating. ## Core Features & Use Cases - CI verification: Watches checks once with gh pr checks --watch, reports green or red honestly, and reads failing job logs before theorizing. - Comment dispositioning: Reads every issue-level and inline review comment via the GitHub CLI and assigns each one apply, defer, or skip with a one-line reason. - Persistent triage record: Posts a ## Review triage table on the PR so the disposition survives the session and queue tooling can detect pending PRs. - Use Case: You opened a PR and a review bot left five inline comments plus one failing check. Run the triage to get a table proposing a disposition per comment, confirm it, apply the fixes as commits, file deferred items as tickets, and record the outcome on the PR. ## Quick Start Ask the assistant to triage the open pull request by checking its CI status and giving every review comment an apply, defer, or skip disposition with reasons.

Frequently Asked Questions about pr-review-triage

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

FAQPage Schema
How do I triage pull request review comments with the GitHub CLI?

Use gh pr view with --comments for issue-level reviews and gh api repos/<owner>/<repo>/pulls/<N>/comments for inline threads. Then assign each comment an apply, defer, or skip disposition with a one-line reason and record the table on the PR.

How to check if a PR's CI checks passed before reviewing comments?

Run gh pr checks <N> --watch --interval 30 to wait for the run once, then gh pr view <N> --json state,mergeable,statusCheckRollup to confirm the result. For failures, read the log with gh run view --job <job-id> --log-failed before concluding anything.

How can I tell if a bot review comment is a real review or a status notice?

Judge by content, not author: a real review names files, lines, or specific claims, while a notice talks about the review itself such as quota limits, queues, or retries. A comment posted seconds after PR creation is almost always a notice, not a review.

Does this skill merge or apply PR changes automatically?

No. It never merges, since merging is a supervised human action, and it never applies changes without explicit human confirmation. It presents a disposition table first and only acts on the accepted items after approval.

What should I do when a bot force-pushes new commits to a PR?

Treat the head SHA as the true identity of what was verified, not the PR number. Re-query gh pr view <N> --json headRefOid,statusCheckRollup before repeating any claim that checks are green, since earlier checks belonged to a commit no longer in the PR.