Individual skill
triage-issue-reports
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.
automations/benny/skills/triage-issue-reports/SKILL.md
Source commit 79595c97d47b5400034fb985e67f1a00389a81af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 21
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- pstack Repository topic
- cline Repository topic
- copilot Repository topic
- gemini Repository topic
- engineering Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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.