skills.rest
sigitpoerwo
sigitpoerwoCOMMUNITY
Explore all skills by this author →
GitHub

pr-status-triage

Triage CI failures and PR review feedback in large monorepos.

Updated Mar 29, 2026
Search Tags:#workflow#debugging#triage#ci#pull-request#continuous-integration#pr-status
One-click install
npx skills add https://github.com/sigitpoerwo/repoworkspace_zahra --skill pr-status-triage-sigitpoerwo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-status-triage
Source: https://github.com/sigitpoerwo/repoworkspace_zahra/tree/main/skills/01-SIAP-PAKAI/business/pr-status-triage
Command: npx skills add https://github.com/sigitpoerwo/repoworkspace_zahra --skill pr-status-triage-sigitpoerwo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage CI failures and PR review comments to speed up debugging and decision making.

Core Features & Use Cases

  • Blocker-first triage: prioritizes build failures, then lint, types, and tests to surface blockers quickly.
  • CI-to-local reproduction: mirrors CI mode and environment variables to reproduce issues locally.
  • Known Flaky Tests awareness: references a known flaky tests list to reduce wasted effort.
  • Use Case: When a PR triggers multiple failing jobs, this skill organizes the triage steps and produces reproducible results.

Quick Start

Run the pr-status-triage script with a PR number to generate a triage report.

Frequently Asked Questions about pr-status-triage

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

FAQPage Schema
How do I triage CI failures and PR review feedback for debugging?▼

To triage CI failures and PR review feedback, apply a blocker-first prioritization approach that surfaces build failures before lint, types, and tests. This streamlines debugging by organizing triage steps and producing reproducible local results.

What is the best way to prioritize multiple failing PR jobs in a large monorepo?▼

The best way to prioritize failing PR jobs in large monorepos is using a blocker-first triage method. This method ranks build failures first, followed by lint, types, and tests, to quickly surface blockers and streamline debugging.

How do I reproduce CI pipeline issues locally for continuous integration debugging?▼

To reproduce CI pipeline issues locally, mirror the CI mode and environment variables used in the continuous integration pipeline. This ensures your local environment matches CI conditions for accurate issue reproduction and debugging.

Do I need specific scripts to run CI triage and reproduce pull-request failures?▼

Yes, you need the scripts/pr-status.js utility and a Known Flaky Tests reference to run CI triage. These components help mirror CI mode and generate reproducible results in the scripts/pr-status/ directory.

How does a known flaky tests reference help streamline CI debugging?▼

A known flaky tests reference streamlines CI debugging by identifying intermittently failing tests. This reduces wasted debugging effort by allowing investigators to skip known flaky tests and focus on genuine pull-request failures.

Where are triage results stored when reproducing CI failures locally?▼

Triage results for CI failures are produced and stored in the scripts/pr-status/ directory. This directory contains the reproducible outputs generated after running the triage script with a specific pull-request number.

Related Skills

Explore More Software Engineering Skills→
JuanDiego30JuanDiego30

pr-status-triage

Triage CI failures and PR review comments with blocker-first prioritization.

Community
Intermediate
vercelvercel
141.7k

pr-status-triage

Triage PR status and CI failures across the Next.js monorepo.

Official
Advanced
mkittmkitt
6

copilot-review

Categorize Copilot pull request comments as Fix, Dismiss, or Decide.

Community
Intermediate
villa1villa1

pr-status-triage

Triage CI failures and PR review feedback from scripts/pr-status.js reports.

Community
Intermediate