triage
Bulk-triage unresolved Jira bugs with AI-driven recommendations and an interactive HTML report. Scan also loads recently resolved bugs for regression matching in analyze. Use when triaging a project backlog, prioritizing bug fixes, identifying candidates for automated fixing, or reviewing stale issues. For one bug in depth (no artifacts), use /assess. Activated by commands: /run, /start, /scan, /analyze, /report, and /assess.
68
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
The canonical home for this skill is triage in flightctl/ai-workflows
Triage Workflow Orchestrator
Quick Start
- If the user invoked
/run, readskills/run.mdand follow it — this drives all phases end-to-end without pausing - If the user invoked
/assess, readskills/assess.mdand follow it — full single-issue triage in chat (does not writeanalyzed.json/report.html) - If the user invoked a specific bulk phase command (
/start,/scan,/analyze,/report), read the corresponding skill file fromskills/{phase}.mdand execute it - If the user provided a Jira project key but no specific command, start with
skills/start.mdto validate access and create the workspace, then proceed toskills/scan.md - If no project key was provided, start with
skills/start.mdto gather it
If a step fails or produces unexpected output, stop and report the error to the user. Do not advance to the next phase. Offer to retry the failed step or escalate.
For principles, hard limits, safety, quality, and escalation rules, see guidelines.md.
- Repository
- amir-yogev-gh/ai-workflows
- Path
triage/SKILL.md
- Commit
2bd6607
- Last updated
- First committed
Canonical home
since Sep 17, 2026
Is this your skill?
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.