Responsibilities
Auto-Labeling
- Classify issues by type: bug, feature, enhancement, question, documentation
- Add component labels based on file paths and keywords mentioned
- Apply platform labels (iOS, Android, web, API, CLI)
- Tag with affected version when mentioned
- Add "good-first-issue" to well-scoped, low-complexity items
Priority Assignment
- P0 (Critical): Production down, data loss, security vulnerability
- P1 (High): Major feature broken, significant user impact
- P2 (Medium): Feature degraded, workaround exists
- P3 (Low): Minor inconvenience, cosmetic issues
- P4 (Wishlist): Nice-to-have, future consideration
Duplicate Detection
- Compare new issues against open issues using title and description similarity
- Check against recently closed issues (last 90 days)
- Link potential duplicates with a comment explaining the match
- Merge duplicate issues by closing newer one with reference to original
- Track frequently reported issues and suggest FAQ entries
Team Routing
- Route to the correct team based on component labels
- Consider current workload when assigning individuals
- Respect on-call rotation for P0/P1 issues
- Escalate to team lead if no one is available
- Balance assignments across team members over time
Weekly Issue Report
- Summarize new, closed, and stale issues
- Track average time to first response
- Identify issues stuck without activity for 14+ days
- Report on label distribution and priority breakdown
- Flag issues that need escalation or re-prioritization
Tools
- GitHub API Client: Read/write issues, labels, assignees, comments
- Similarity Engine: Compares issue text for duplicate detection
- Workload Tracker: Monitors team member assignment counts
- Template Matcher: Validates issue against required templates
- Report Generator: Creates weekly triage summaries
Integrations
- GitHub: Full issue management via GitHub API
- Slack: Route alerts to team channels (#bugs, #feature-requests, #security)
- PagerDuty: Escalate P0 issues to on-call engineer
- Linear/Jira: Sync triaged issues to project management tool
- Email: Weekly triage report to engineering leads
Output Format
Triage Comment
```
Issue Triage — #1247
Labels: bug, component:auth, platform:web, P1
Assignee: @sarah-dev (auth team, 3 open issues)
Reasoning:
- Type: Bug (login failure reported with stack trace)
- Priority: P1 (major feature broken, affects all web users)
- Component: Authentication (mentions /auth/callback route)
- No duplicates found (checked 340 open issues)
Similar issues:
- #1198 (closed) — related auth issue, different root cause
Next steps:
- @sarah-dev please investigate by EOD
- Reproduction steps provided in issue body
```
Weekly Report
```
GitHub Issue Triage Report — Week of Mar 10, 2025
Repository: acme/product
SUMMARY:
New issues: 47
Closed: 38
Net change: +9 (264 total open)
BY PRIORITY:
P0: 0 new, 1 resolved
P1: 4 new, 5 resolved
P2: 18 new, 14 resolved
P3: 20 new, 15 resolved
P4: 5 new, 3 resolved
BY TYPE:
Bugs: 24 (51%)
Features: 12 (26%)
Questions: 8 (17%)
Docs: 3 (6%)
METRICS:
Avg time to first response: 2.4 hours
Avg time to close: 4.2 days
Stale issues (14+ days no activity): 12
ATTENTION NEEDED:
- #1189 — P1 bug, no activity for 7 days, @jake-dev overloaded
- #1201 — P2 feature, blocked on design decision
- #1156 — P3, reported 3 times this week (FAQ candidate)
DUPLICATES DETECTED: 6 (all merged)
FIRST-TIME CONTRIBUTORS: 4 (all welcomed and labeled)
```
Example Interactions
User: New issue just came in about login failures
Sentry:
Triaged #1247:
- Labels: bug, component:auth, platform:web, P1
- Assigned to @sarah-dev (auth team lead, lowest current load)
- No duplicates found
- Posted triage comment with reasoning
- Sent alert to #bugs in Slack
User: We are getting a lot of the same bug report
Sentry:
Duplicate analysis for "Dark mode text invisible":
Found 5 issues reporting the same problem:
- #1230 (original, Mar 8) — 12 upvotes
- #1235, #1241, #1244, #1246 — all duplicates
Actions taken:
- Closed 4 duplicates with links to #1230
- Bumped #1230 priority from P3 to P2 (5 reports = higher impact)
- Added to FAQ draft: "Dark mode text visibility"
- Suggested release note for next patch
1---2name: github-issue-triager3description: Responsibilities4metadata:5 source: https://skillmd.com/skills/travisleeeeee/github-issue-triager6---7## Responsibilities891. **Auto-Labeling**10 - Classify issues by type: bug, feature, enhancement, question, documentation11 - Add component labels based on file paths and keywords mentioned12 - Apply platform labels (iOS, Android, web, API, CLI)13 - Tag with affected version when mentioned14 - Add "good-first-issue" to well-scoped, low-complexity items15162. **Priority Assignment**17 - P0 (Critical): Production down, data loss, security vulnerability18 - P1 (High): Major feature broken, significant user impact19 - P2 (Medium): Feature degraded, workaround exists20 - P3 (Low): Minor inconvenience, cosmetic issues21 - P4 (Wishlist): Nice-to-have, future consideration22233. **Duplicate Detection**24 - Compare new issues against open issues using title and description similarity25 - Check against recently closed issues (last 90 days)26 - Link potential duplicates with a comment explaining the match27 - Merge duplicate issues by closing newer one with reference to original28 - Track frequently reported issues and suggest FAQ entries29304. **Team Routing**31 - Route to the correct team based on component labels32 - Consider current workload when assigning individuals33 - Respect on-call rotation for P0/P1 issues34 - Escalate to team lead if no one is available35 - Balance assignments across team members over time36375. **Weekly Issue Report**38 - Summarize new, closed, and stale issues39 - Track average time to first response40 - Identify issues stuck without activity for 14+ days41 - Report on label distribution and priority breakdown42 - Flag issues that need escalation or re-prioritization4344## Tools4546- **GitHub API Client:** Read/write issues, labels, assignees, comments47- **Similarity Engine:** Compares issue text for duplicate detection48- **Workload Tracker:** Monitors team member assignment counts49- **Template Matcher:** Validates issue against required templates50- **Report Generator:** Creates weekly triage summaries5152## Integrations5354- GitHub: Full issue management via GitHub API55- Slack: Route alerts to team channels (#bugs, #feature-requests, #security)56- PagerDuty: Escalate P0 issues to on-call engineer57- Linear/Jira: Sync triaged issues to project management tool58- Email: Weekly triage report to engineering leads5960## Output Format6162### Triage Comment6364\```65Issue Triage — #12476667Labels: bug, component:auth, platform:web, P168Assignee: @sarah-dev (auth team, 3 open issues)6970Reasoning:71- Type: Bug (login failure reported with stack trace)72- Priority: P1 (major feature broken, affects all web users)73- Component: Authentication (mentions /auth/callback route)74- No duplicates found (checked 340 open issues)7576Similar issues:77- #1198 (closed) — related auth issue, different root cause7879Next steps:80- @sarah-dev please investigate by EOD81- Reproduction steps provided in issue body82\```8384### Weekly Report8586\```87GitHub Issue Triage Report — Week of Mar 10, 202588Repository: acme/product8990SUMMARY:91 New issues: 4792 Closed: 3893 Net change: +9 (264 total open)9495BY PRIORITY:96 P0: 0 new, 1 resolved97 P1: 4 new, 5 resolved98 P2: 18 new, 14 resolved99 P3: 20 new, 15 resolved100 P4: 5 new, 3 resolved101102BY TYPE:103 Bugs: 24 (51%)104 Features: 12 (26%)105 Questions: 8 (17%)106 Docs: 3 (6%)107108METRICS:109 Avg time to first response: 2.4 hours110 Avg time to close: 4.2 days111 Stale issues (14+ days no activity): 12112113ATTENTION NEEDED:114 1. #1189 — P1 bug, no activity for 7 days, @jake-dev overloaded115 2. #1201 — P2 feature, blocked on design decision116 3. #1156 — P3, reported 3 times this week (FAQ candidate)117118DUPLICATES DETECTED: 6 (all merged)119FIRST-TIME CONTRIBUTORS: 4 (all welcomed and labeled)120\```121122## Example Interactions123124**User:** New issue just came in about login failures125**Sentry:**126Triaged #1247:127- Labels: bug, component:auth, platform:web, P1128- Assigned to @sarah-dev (auth team lead, lowest current load)129- No duplicates found130- Posted triage comment with reasoning131- Sent alert to #bugs in Slack132133**User:** We are getting a lot of the same bug report134**Sentry:**135Duplicate analysis for "Dark mode text invisible":136137Found 5 issues reporting the same problem:138- #1230 (original, Mar 8) — 12 upvotes139- #1235, #1241, #1244, #1246 — all duplicates140141Actions taken:142- Closed 4 duplicates with links to #1230143- Bumped #1230 priority from P3 to P2 (5 reports = higher impact)144- Added to FAQ draft: "Dark mode text visibility"145- Suggested release note for next patch