From one-horizon
Turn open bugs into triage notes a team can actually use. Use when asked "prepare bug triage", "summarize open bugs", or "prioritize defects for review". Requires One Horizon MCP.
npx claudepluginhub onehorizonai/skills --plugin one-horizonThis skill uses the workspace's default tool permissions.
Turn a list of open bugs into clear triage notes with enough context to decide priority and next action.
Triages bugs by player impact, reproducibility, severity, and milestone risk for prioritization. Useful when defect counts rise, milestone pressure mounts, or teams disagree on priority.
Triages issues in project trackers using state machine with bug/enhancement categories and states like needs-triage, needs-info. Reproduces bugs, generates agent briefs, applies labels, closes issues.
Classifies, deduplicates, prioritizes, and dispatches raw incoming issues into actionable work items for dev agents. Use for GitHub issues or external sources.
Share bugs, ideas, or general feedback.
Turn a list of open bugs into clear triage notes with enough context to decide priority and next action.
Assess each bug using concrete signals:
list-bugs.get-task-details when the title or summary is too thin to triage responsibly.### headings for bug titles.### <bug title>
Short TLDR paragraph:
In 2-4 sentences, summarize what is broken, who is affected, how reliable the repro is, and why this bug should or should not be prioritized now.
### Background
- One short paragraph on the affected workflow and what is happening today.
### Repro and evidence
- Best known repro steps or trigger conditions.
- Evidence quality: confirmed, partial, or unclear.
### Known scope / boundaries
- Where this bug shows up.
- What appears unaffected or still unconfirmed.
### Impact and workaround
- What the user cannot do.
- Whether a workaround exists.
### Triage recommendation
- Suggested priority with a short reason.
- Suggested next action such as investigate, assign, merge with duplicate, wait for more evidence, or close.
### Open questions
- What is still missing to make a confident call?
Use direct language:
Highest priority: blocks a core workflow, has broad reach, or has no workaround.High priority: serious user pain with solid evidence, but not a total blocker.Medium priority: real issue, narrower scope, partial workaround, or weaker evidence.Low priority: edge case, unclear repro, cosmetic issue, or low user impact.If confidence is low, say that clearly instead of pretending the triage is settled.
For every triage recommendation, be explicit about confidence:
High confidence: strong repro or evidence, clear impact, little ambiguity.Medium confidence: likely real, but one of repro, reach, or scope is still fuzzy.Low confidence: weak evidence, unclear repro, or likely duplicate/noise.Do not present a shaky recommendation as definitive.