pr-status-triage

Name: pr-status-triage
Availability: InStock
Author: juandiego30

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

Updated Apr 14, 2026

Search Tags:#automation #workflow #blockers #pr #triage #ci

Ready to run

npx skills add https://github.com/JuanDiego30/cermont_aplicativo --skill pr-status-triage-juandiego30

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-status-triage
Source: https://github.com/JuanDiego30/cermont_aplicativo/tree/main/.agents/skills/pr-status-triage
Command: npx skills add https://github.com/JuanDiego30/cermont_aplicativo --skill pr-status-triage-juandiego30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage CI failures and PR review comments to surface blockers and reduce MTTR during development and code reviews.

Core Features & Use Cases

Blocker-first prioritization: prioritize build, lint, types, then tests to focus on blockers.
Local reproduction guidance: reuse CI env var matching to reproduce failures locally.
Known flaky tests handling: distinguish flaky tests from real failures to avoid noise.

Quick Start

Run node scripts/pr-status.js to generate the triage report for the latest PR.

Frequently Asked Questions about pr-status-triage

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

FAQPage Schema

How do I prioritize CI failures in a PR workflow?▼

You can automate CI failure triage by running the pr-status script to generate a report that surfaces blockers using a build, lint, types, then tests prioritization hierarchy.

How do I reproduce CI failures locally using environment variables?▼

Reproduce CI failures locally by mapping CI environment variables to your local shell, matching the execution context to replicate the exact conditions under which the pipeline failed.

How do I distinguish known flaky tests from real failures?▼

Distinguish flaky tests from real failures by implementing known flaky test handling that filters pre-identified inconsistent tests from the triage report, reducing noise during PR reviews.

What is the best way to triage PR review comments in a monorepo?▼

Automating triage in a monorepo aggregates PR review comments and CI failures into a single report that surfaces blockers, reducing mean time to resolution during code reviews.

Can I use this triage approach for flaky test investigations?▼

Yes, you can use this triage approach for flaky test investigations because it explicitly handles known flaky tests, separating them from genuine CI failures to avoid noise.

Why does my CI pipeline prioritize build errors over test failures?▼

CI pipelines prioritize build errors over test failures because a failed build prevents the application from compiling, making it the highest blocker before lint, types, or tests can run.