skills.rest
primeinc
primeincCOMMUNITY
Explore all skills by this author →
GitHub

pr-triage

Prioritize human feedback and surface actionable GitHub PR comments.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/primeinc/swarm --skill pr-triage-primeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-triage
Source: https://github.com/primeinc/swarm/tree/main/.opencode/skill/pr-triage
Command: npx skills add https://github.com/primeinc/swarm --skill pr-triage-primeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires zod, and includes scripts (resource) and references (resource) components.

What problem does it solve?

PR comment triage often incurs heavy context-switching during code reviews. This skill automates context-efficient triage by prioritizing human feedback, deferring non-critical bot noise, and surfacing actionable items for faster resolutions.

Core Features & Use Cases

  • On-demand metadata fetch for PR comments (compact ~100 bytes per item) to enable quick triage without loading full bodies
  • Bot vs. human prioritization and smart triage, with refinement after fetching relevant comment bodies
  • Ability to reply to actionable comments or resolve threads to reduce noise and keep PR reviews focused
  • Per-file summaries and batch actions to help teams coordinate across files

Quick Start

Use bun run pr-comments.ts list owner/repo 42 to fetch metadata, then bun run pr-comments.ts triage owner/repo 42 to prioritize comments, and bun run pr-comments.ts expand owner/repo 123456 to fetch a specific comment body when needed.

Frequently Asked Questions about pr-triage

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

FAQPage Schema
How do I automate GitHub pull request comment triage to reduce context switching?▼

Automate GitHub pull request comment triage by fetching compact metadata (~100 bytes per item), prioritizing human feedback over bot noise, and surfacing actionable items to reduce context switching during code reviews.

What is the best way to filter bot noise from human feedback in PR reviews?▼

Filter bot noise from PR reviews using bot-vs-human prioritization, which defers non-critical bot comments and surfaces human feedback first to keep code review focus on actionable issues.

How do I fetch specific PR comment bodies on demand without loading the full thread?▼

Fetch specific PR comment bodies on demand by expanding individual comments via their ID after triage, retrieving full text only when needed rather than loading the entire thread initially.

Can I batch resolve PR threads and reply to comments directly from a triage script?▼

Batch resolve PR threads and reply to comments directly using scripted reply and resolve workflows, enabling coordinated batch actions across files to reduce noise and keep reviews focused.

Do I need bun runtime to run PR triage scripts for GitHub repositories?▼

Use bun runtime to execute PR triage scripts like fetching metadata, triaging comments, and expanding specific comment bodies for GitHub repositories efficiently.

When should I avoid on-demand comment expansion during PR triage?▼

Avoid on-demand comment expansion when PR reviews contain few comments, as compact metadata retrieval and bot prioritization provide the most context efficiency benefits during large reviews with heavy comment volume.

Related Skills

BindBind
5

github-pr

Automate GitHub PR review triage, guideline discovery, and inline comments.

Community
Intermediate
drillandrillan
1

review-pr-comments

Group GitHub pull request comments by file and thread for decision making.

Community
Advanced
joi-fairsharejoi-fairshare
1

addressReview

Merge human PR feedback with structured issues and coordinate parallel implementation agents.

Community
Advanced
wyhlovecppwyhlovecpp

gh-address-comments

Retrieve and organize GitHub PR review comments and threads via gh CLI and GraphQL API.

Community
Basic