Triage incoming software issue reports using available repository and runtime evidence, without editing code. Use for automated or manual first-pass issue validation and routing.
Installs into .claude/skills of the current project.
Are you the author of Triage Issue Reports?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/theonlyfusioncube-triage-issue-reports)
---
name: triage-issue-reports
description: Triage incoming software issue reports using available repository and runtime evidence, without editing code. Use for automated or manual first-pass issue validation and routing.
---
# Triage issue reports
1. Normalize the report into product area, environment, steps, expected behavior, observed behavior, frequency, and supplied evidence.
2. Search for duplicates and known limitations when issue/search capabilities exist.
3. Inspect the relevant code/feature map enough to judge plausibility without making edits.
4. Classify as confirmed-enough-to-reproduce, needs-reporter-information, duplicate, expected behavior, or currently untriageable.
5. Reply in the source thread/ticket when available with concise rationale and the next action. Do not invent a reproduction.
