c3f43d8b61
- Add 60 new agents across all 10 categories (75 -> 135) - Add 95 new plugins with command files (25 -> 120) - Update all agents to use model: opus - Update README with complete plugin/agent tables - Update marketplace.json with all 120 plugins
1.4 KiB
1.4 KiB
/triage-issues - Triage GitHub Issues
Analyze and triage open GitHub issues for prioritization.
Steps
- Fetch all open issues from the repository using the GitHub API
- Filter issues by: unlabeled, unassigned, or stale (no activity in 30 days)
- Analyze each issue for: completeness, reproducibility, severity, and impact
- Suggest labels based on issue content: bug, feature, enhancement, documentation, question
- Assess priority based on: user impact, frequency of reports, component affected
- Identify duplicate issues by comparing titles and descriptions with existing issues
- Flag issues that need more information from the reporter
- Group related issues that could be addressed together
- Suggest assignees based on the component or area affected
- Create a triage summary: total open, by priority, by label, stale issues
- Recommend which issues to close (duplicates, won't fix, cannot reproduce)
- Generate a prioritized backlog view for the next sprint
Rules
- Do not close issues without user confirmation
- Respect existing labels and assignments; suggest changes, do not override
- Mark issues as stale only if truly inactive (no comments, no linked PRs)
- Prioritize bugs over features, security issues over all others
- Consider the number of thumbs-up reactions as a popularity signal
- Do not auto-assign issues; suggest assignees for human decision
- Keep triage notes factual and neutral in tone