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
- Installs
- 379
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/withastro/astro --skill triage- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads triage automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
issueTitleandissueBodyprovided in args (preferred — use these directly as the bug report), OR- A GitHub issue number or URL mentioned in the conversation (use
gh issue viewto 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. 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. 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. 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. 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.
FAQ
What does the triage skill do?
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
How do I install triage?
Run npx skills add https://github.com/withastro/astro --skill triage in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/triage/ (personal) or .claude/skills/triage/ (project).
Which AI agents can use triage?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is triage safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains triage?
It is published by withastro in withastro/astro. It has 379 recorded installs.
More from withastro/astro
astro-developer
withastro/astro
Comprehensive guide for developing in the Astro monorepo. Covers architecture, debugging, testing, and critical constraints. Use when working on features, fixes, tests, or understanding the codebase structure.
analyze-github-action-logs
withastro/astro
Open the skill to read its SKILL.md instructions.
astro-pr-writer
withastro/astro
Open the skill to read its SKILL.md instructions.
astro-code-review
withastro/astro
Open the skill to read its SKILL.md instructions.
changeset
withastro/astro
Create a changeset for the Astro monorepo. Use this skill whenever you need to add a changeset file to a PR, write a changelog entry, or document a package version bump. Also trigger when the user says "add a changeset", "write a changeset", "create a changeset", or when another skill instructs you to create a changeset.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.