Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

pr-status-triage

Estrelas140.200

Forks31.287

Atualizado14 de maio de 2026 às 20:29

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

vercel

vercel/next.js

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	pr-status-triage
description	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.
metadata	{"internal":true}

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/results/index.md.
Analyze each job-{id}.md and thread-{N}.md file in scripts/pr-status/results/ 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. Use reply-and-resolve-thread to do both in one step, or use reply-thread + resolve-thread separately. See scripts/pr-status/results/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

Thread interaction:

node scripts/pr-status.js reply-thread <threadNodeId> "<body>"           # reply to a review thread
node scripts/pr-status.js resolve-thread <threadNodeId>                  # resolve a review thread
node scripts/pr-status.js reply-and-resolve-thread <threadNodeId> "<body>"  # reply and resolve in one step

References

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

Mais deste repositório

mesmo repositório

gh-stack

vercel/next.js

Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.

2026-07-07140.4k

insight-error-page

vercel/next.js

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new `errors/<slug>.mdx` page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification against canonical docs, and Vercel technical writing style.

2026-07-01140.4k

next-cache-components-adoption

vercel/next.js

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work through a flood of blocking-prerender / instant validation errors, run the `cache-components-instant-false` codemod, or decide between opting routes out with `export const instant = false` and fixing them in place.

2026-06-29140.4k

next-dev-loop

vercel/next.js

Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.

2026-06-26140.4k

flags

vercel/next.js

How to add or modify Next.js experimental feature flags end-to-end. Use when editing config-shared.ts, config-schema.ts, define-env-plugin.ts, next-server.ts, export/worker.ts, or module.compiled.js. Covers type declaration, zod schema, build-time injection, runtime env plumbing, and the decision between runtime env-var branching vs separate bundle variants.

2026-06-24140.4k

next-rspack

vercel/next.js

Maintain @next/rspack-core and @next/rspack-binding packages. Use when editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json. Covers upgrading @rspack/core npm version, rspack_* crate versions, Rust toolchain version, building and linking for local testing, and NEXT_RSPACK environment variable usage. Does NOT apply to root rust-toolchain.toml (that's for Turbopack).

2026-06-22140.4k

name	pr-status-triage
description	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.
metadata	{"internal":true}

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/results/index.md.
Analyze each job-{id}.md and thread-{N}.md file in scripts/pr-status/results/ 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. Use reply-and-resolve-thread to do both in one step, or use reply-thread + resolve-thread separately. See scripts/pr-status/results/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

Thread interaction:

node scripts/pr-status.js reply-thread <threadNodeId> "<body>"           # reply to a review thread
node scripts/pr-status.js resolve-thread <threadNodeId>                  # resolve a review thread
node scripts/pr-status.js reply-and-resolve-thread <threadNodeId> "<body>"  # reply and resolve in one step

References

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