How do I install the Pr Status Triage skill?

Run npx skillmds@latest add mahabdalla/pr-status-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Status Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Status Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Status Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Status Triage?

mahabdalla (@mahabdalla) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Status Triage by mahabdalla — Agent Skill

Name: Pr Status Triage
Rating: 4.666666666666667 (3 reviews)
Author: mahabdalla

Pr Status Triage

Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction.

mahabdalla Updated Sep 22, 2026

File contents

PR Status Triage

Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.

Workflow

Run node scripts/pr-status.js --wait in the background (timeout 1 min), then read scripts/pr-status/index.md.
Analyze each job-{id}.md and thread-{N}.md file for failures and review feedback.
Prioritize blocking jobs first: build, lint, types, then test jobs.
Treat failures as real until disproven; check the "Known Flaky Tests" section before calling anything flaky.
Reproduce locally with the same mode and env vars as CI.
After addressing review comments, reply to the thread describing what was done, then resolve it. See thread-N.md files for ready-to-use commands.
When the only remaining failures are known flaky tests and no code changes are needed, retrigger the failing CI jobs with gh run rerun <run-id> --failed. Then wait 5 minutes and go back to step 1. Repeat this loop up to 5 times.

Quick Commands

node scripts/pr-status.js                  # current branch PR
node scripts/pr-status.js <number>         # specific PR
node scripts/pr-status.js [PR] --wait      # background mode, waits for CI to finish
node scripts/pr-status.js --skip-flaky-check  # skip flaky test detection

References

workflow.md — prioritization, common failure patterns, resolving review threads
local-repro.md — mode/env matching and isolation guidance

Converted and distributed by TomeVault | Claim this content

---name: pr-status-triagedescription: Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction.---# PR Status TriageUse this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.## Workflow1. Run `node scripts/pr-status.js --wait` in the background (timeout 1 min), then read `scripts/pr-status/index.md`.2. Analyze each `job-{id}.md` and `thread-{N}.md` file for failures and review feedback.3. Prioritize blocking jobs first: build, lint, types, then test jobs.4. Treat failures as real until disproven; check the "Known Flaky Tests" section before calling anything flaky.5. Reproduce locally with the same mode and env vars as CI.6. After addressing review comments, reply to the thread describing what was done, then resolve it. See `thread-N.md` files for ready-to-use commands.7. When the only remaining failures are known flaky tests and no code changes are needed, retrigger the failing CI jobs with `gh run rerun <run-id> --failed`. Then wait 5 minutes and go back to step 1. Repeat this loop up to 5 times.## Quick Commands```bashnode scripts/pr-status.js # current branch PRnode scripts/pr-status.js <number> # specific PRnode scripts/pr-status.js [PR] --wait # background mode, waits for CI to finishnode scripts/pr-status.js --skip-flaky-check # skip flaky test detection```## References- [workflow.md](./workflow.md) — prioritization, common failure patterns, resolving review threads- [local-repro.md](./local-repro.md) — mode/env matching and isolation guidance---> Converted and distributed by [TomeVault](https://tomevault.io) | [Claim this content](https://tomevault.io/claim/vercel/next.js)

Frequently asked questions