skills.rest
vercel
vercelOFFICIAL
Explore all skills by this author →
Website𝕏@vercelGitHub

pr-status-triage

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

142k|31.7k|Updated Oct 5, 2016
Search Tags:#automation#workflow#nodejs#triage#ci#pull-request
One-click install
npx skills add https://github.com/vercel/next.js --skill pr-status-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-status-triage
Source: https://github.com/vercel/next.js/tree/main/.agents/skills/pr-status-triage
Command: npx skills add https://github.com/vercel/next.js --skill pr-status-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Run node scripts/pr-status.js to analyze the current PR and open reports for job and thread status.
  • Prioritize blocking jobs first: build, lint, types, then tests, to focus on the most impactful failures.
  • Reproduce locally with the same mode and environment variables as CI to verify failures.
  • Read and resolve PR threads using ready-to-use commands described in thread-N.md files.

Quick Start

Start triaging by running node scripts/pr-status.js in the current branch, then inspect the generated reports and follow the step-by-step commands.

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 and PR review threads for debugging?▼

Prioritize CI failures by resolving blocking jobs first—build, then lint, types, and tests—to focus debugging on the most impactful PR blockers before addressing lower-priority issues.

What is the best way to reproduce failing CI jobs locally?▼

Reproduce failing CI jobs locally by matching the exact CI environment variables and execution mode used during the pull request pipeline to verify the failures on your own machine.

How do I triage flaky tests in a Next.js monorepo pull request?▼

Triage flaky tests by running the PR status triage script to analyze job outputs, which distinguishes known flaky tests from genuine blockers to guide your debugging decisions across the monorepo.

Do I need the GitHub CLI to manage pull request threads and CI status?▼

Yes, you need a local GitHub CLI environment to reproduce CI threads, read thread-N.md reports, and execute ready-to-use commands for resolving pull request review feedback efficiently.

How does blocker-first prioritization work for CI triage?▼

Blocker-first prioritization ranks CI failures by impact—build failures block everything, followed by lint, types, and tests—ensuring you fix upstream issues before investigating downstream test failures.

Related Skills

Explore More Software Engineering Skills→
villa1villa1

pr-status-triage

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

Community
Intermediate
muklesmukles

resolve-pr-feedback

Evaluate and resolve unresolved GitHub PR review threads with fixes or replies.

Community
Advanced
erclxerclx
2

claude-address-review

Apply code fixes and update documentation for GitHub pull request review findings.

Community
Advanced
JuanDiego30JuanDiego30

pr-status-triage

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

Community
Intermediate