triage-issue
Triage OpenDataSuite GitHub issues — assign milestone and labels per docs/ROADMAP.md, detect duplicates, and check acceptance criteria are testable. Use for new issues, backlog grooming, or when asked
Files1
View on GitHubSKILL.mdskills/triage-issue/SKILL.md
GitHubTriage
- Fetch the issue(s). Search for duplicates by title/topic (
search_issues), and check ROADMAP §5. - Pick the milestone using ROADMAP §4 — the earliest milestone whose release needs it. Anything not required by M0–M6 goes to M7/M8/M9.
- Pick labels from
.github/labels.json: exactly onetype:*, one or morearea:*,provider:*if vendor-specific,priority:critical-pathif it blocks a release. - Check acceptance criteria are verifiable; if not, draft sharper criteria.
- Write changes to the repo files first (
.github/milestones.json, ROADMAP tables), then apply to GitHub withscripts/sync-milestones.sh(or MCPissue_write) — only when the user has asked you to modify GitHub. Otherwise present the proposal. - Closing duplicates: comment
Duplicate of #N, close withstate_reason: duplicate, and only with user approval.