Opt-in workflow for triaging one GitHub issue without fixing it. Invoked only via `/triage <github-issue-url>` (`$triage` in Codex). Establishes live state, reproduces with our own fixtures, probes real Next.js for parity, classifies the issue, and drafts the issue reply and next action. Hands valid bugs off to the fix step.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Issue: $ARGUMENTS
Establish the issue's live state below, then follow references/rules.md for everything else: safety, the parity check, reproducing, the verdict and the reply. Its "Automated Runs" section doesn't apply here. In those rules, "the fix step" means the fix skill (/fix <github-issue-url>, $fix in Codex).
Do not open a PR, post a comment, change labels or close the issue without confirmation.
Require one GitHub issue URL, passed as the /triage argument. If it is missing, ask for it. If it names a repository other than the current checkout, find an existing checkout of that repository before reading code.
git fetch origin main and compare it with the checkout's HEAD. A stale checkout produces "already fixed" mistakes.gh issue view --comments. Before any multi-issue sweep, run gh api rate_limit, estimate the cost, keep first: small, prefer REST or gh search, and stop when fewer than ~1,500 calls remain.gh.gh pr list --search "<number>", git log origin/main --grep). If a PR exists, check its state with gh pr view <n> --json state before suggesting any follow-up on it.Then work through references/rules.md.
Report to the user:
Post the comment, change labels or close the issue only after the user confirms.
cloudflare/vinext
b0587b3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.