pr-triage

Triage automated bot review comments on GitHub pull requests before merging.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/rp4ri/orchestration-studio --skill pr-triage-rp4ri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-triage
Source: https://github.com/rp4ri/orchestration-studio/tree/main/skills/pr-triage
Command: npx skills add https://github.com/rp4ri/orchestration-studio --skill pr-triage-rp4ri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical issue of unaddressed automated bot review comments on GitHub pull requests, which lead to broken merges, post-merge bugs, and wasted engineering time chasing unresolved feedback in high-velocity repositories.

Core Features & Use Cases

  • Accurate Unanswered Comment Counting: Eliminates false positives from early bot review cycles by requiring two consecutive all-zero polls and a minimum review count before declaring a PR triaged.
  • Structured Triage Workflow: Guides users to fix legitimate bot observations with referenced commit SHAs or justify rejections with concrete, in-thread reasoning, ensuring no bot feedback is left unaddressed.
  • Merge Safety & Coordination: Gates merges on zero unanswered comments and mergeable status, automatically handles merge conflicts from dependent PRs, and closes superseded PRs with links to their replacements.
  • Use Case: Ideal for engineering teams using automated review tools (Gemini Code Assist, Codex, etc.) running multi-agent orchestration workflows, where maintaining a clean, conflict-free PR queue is critical for release velocity.

Quick Start

Use the pr-triage skill to triage all unresolved bot review comments on open PR #42, fix legitimate issues with commits, reply to invalid comments with clear reasoning, and merge the PR once all bot feedback is fully addressed.

Frequently Asked Questions about pr-triage

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

FAQPage Schema
How do I ensure there are zero unanswered bot review comments before merging a GitHub pull request?

To ensure zero unanswered bot review comments before merging, gate the pull request on a structured triage workflow that requires two consecutive all-zero polling cycles and a minimum review count to confirm all automated feedback is fully resolved.

What is the best way to triage automated code review bot feedback on high-velocity GitHub repositories?

The best way to triage automated code review bot feedback is to apply severity heuristics for prioritizing critical observations, fix legitimate issues with referenced commit SHAs, and justify rejections with concrete in-thread reasoning.

Can I use automated triage workflows with code review tools like Gemini Code Assist and Codex?

Yes, automated triage workflows explicitly support code review tools like Gemini Code Assist and Codex, coordinating multiple PR merges and delegating workers for director-led multi-agent orchestration in high-velocity engineering environments.

How do you coordinate merging multiple dependent GitHub pull requests with automated bot reviews?

Coordinate merging multiple dependent pull requests by checking mergeable status alongside zero unanswered comments, automatically handling merge conflicts from dependent PRs, and closing superseded PRs with links to their replacements.

Why does my automated bot review cycle falsely declare a pull request triaged before it is finished?

Premature merge declarations from incomplete bot review cycles occur when initial zero polls happen early, which is prevented by requiring two consecutive all-zero polling cycles and a minimum review count before declaring a pull request triaged.