What problem does it solve? Repository maintainers receive bug reports that mix expected behavior, observed behavior, and incomplete reproduction steps, making it hard to decide what to do next. This Skill turns a raw issue into a structured triage note grounded in cited evidence. ## Core Features & Use Cases - Structured Issue Breakdown: Separates expected behavior, observed behavior, affected version, and reproduction steps, explicitly marking missing information. - Evidence-Cited Findings: Locates the affected code or documentation and cites a file or link per finding, labeling hypotheses distinctly from confirmed facts. - Duplicate Comparison: Compares symptoms, versions, and root-cause evidence against existing issues before suggesting duplicates, or states that no duplicate search was performed. - Use Case: A maintainer receives a report that a slug function preserves punctuation on Python 3.11 with attached input and expected output. The Skill produces a draft note with a summary, evidence, missing details, suggested category, severity based on user impact, and the smallest next action. ## Quick Start Ask the assistant to triage a pasted GitHub issue report and produce a draft triage note with evidence, missing details, and a suggested next action.