Skip to main content

triage

Triage a bug report. Reproduces the bug, diagnoses the root cause, verifies whether the behavior is intentional, and attempts a fix. Use when asked to "triage issue

Jump to install

Source facts

Repository
withastro/astro
Last source activity
August 20, 2026 at 12:44
Detected SKILL.md language
English
Stars
62,721
Forks
3,798

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
6 files

Showing SKILL.md

SKILL.md
Source instructions ยท Read-only preview
name
triage
description
Triage a bug report. Reproduces the bug, diagnoses the root cause, verifies whether the behavior is intentional, and attempts a fix. Use when asked to "triage issue
# Triage Triage a bug report end-to-end: reproduce the bug, diagnose the root cause, verify whether the behavior is intentional, and attempt a fix. ## General Rules **Do not get stuck on infrastructure problems.** If a server won't start, a port is blocked, or a tool is unavailable in the CI environment โ€” bail out after 2 attempts and write your report with the data you already have. Looping on server restarts or missing CLI tools wastes your entire time budget. A partial report with solid findings is infinitely more valuable than no report because you ran out of time fighting a stale process. ## Input You need either: - `issueTitle` and `issueBody` provided in args (preferred โ€” use these directly as the bug report), OR - A GitHub issue number or URL mentioned in the conversation (use `gh issue view` to fetch details) If a `triageDir` is provided in args, use that as the working directory for the triage. Otherwise, default to `triage/gh-<issue_number>` (if you have an issue number) or `triage/current`. ## Step 1: Reproduce Read and follow [reproduce.md](reproduce.md). Use a subagent for this step to isolate context. After completing reproduction, check the result: - If the issue was **skipped** (host-specific, unsupported version, etc.) โ€” skip to Output. - If the issue was **not reproducible** โ€” skip to Output. - If the issue was **reproduced** โ€” continue to Step 2. ## Step 2: Diagnose Read and follow [diagnose.md](diagnose.md). Use a subagent for this step to isolate context. After completing diagnosis, check your confidence: - If confidence is **low** โ€” skip to Output. - If confidence is **medium** or **high** โ€” continue to Step 3. ## Step 3: Verify Read and follow [verify.md](verify.md). Use a subagent for this step to isolate context. After completing verification, check the verdict: - If the verdict is **intended-behavior** โ€” skip to Output. The issue is not a bug; do not attempt a fix. - If the verdict is **bug** or **unclear** โ€” continue to Step 4. ## Step 4: Fix Read and follow [fix.md](fix.md). Use a subagent for this step to isolate context. Whether the fix succeeds or fails, continue to Output. ## Output After completing the triage (or exiting early), return your structured results so the orchestrator can post a comment and manage labels.
View on GitHub