Issue Triage Guidance
Gather open issues and PRs, analyze them, and recommend next steps. Search the codebase to identify affected components — don't rely on hardcoded file mappings.
Priority Definitions
| Priority |
Criteria |
| 🔴 Critical |
Production broken, security issue, data loss |
| 🟠 High |
Major feature broken, blocking users |
| 🟡 Medium |
Feature degraded, workaround exists |
| 🟢 Low |
Minor issue, cosmetic, nice-to-have |
Complexity Scale
| Size |
Estimate |
| S |
Hours |
| M |
1-2 days |
| L |
3-5 days |
| XL |
1+ week |
Label Taxonomy
| Prefix |
Values |
area: |
backend, frontend, auth, streaming, infra, docs |
type: |
bug, feature, enhancement, chore, docs |
priority: |
critical, high, medium, low |
Triage Report Format
Open Issues Summary
| # |
Title |
Priority |
Type |
Complexity |
Per Issue — #[number]: [title]
- Priority / Type / Complexity
- Affected Areas: checklist of areas
- Relevant Files: table with file + reason
- Suggested Labels: using taxonomy above
- Recommended Next Steps: numbered list
Open PRs Summary
| # |
Title |
Author |
Status |
Files Changed |
Per PR — #[number]: [title]
- Status: Draft | Ready for review | Changes requested | Approved
- Review Notes: concerns or things to check
gh CLI Commands for Read-Only Analysis
# List open issues
gh issue list --state open
# Search for potential duplicates
gh issue list --search "keyword"
# View issue details
gh issue view <number>
# List open PRs
gh pr list --state open
# View PR details and diff
gh pr view <number>
gh pr diff <number>
Duplicate Detection
Before deep-diving into an issue, search for duplicates:
- Use
gh issue list --search "<keywords>" with key terms from the issue title and body.
- Check closed issues too:
gh issue list --state closed --search "<keywords>".
- If a duplicate exists, note it in the triage report with a cross-reference.
Constraints
- ❌ Read-only — do NOT modify issues or PRs
- ❌ No
gh issue edit, gh issue close, gh issue label
- ❌ No
gh pr merge, gh pr close, gh pr review --approve
- ✅ Only use read commands:
list, view, search, diff
1---2name: triaging-issues3description: >4 Provides issue triage workflow, priority definitions, and report format.5 Use when analyzing GitHub issues and PRs, assessing priority,6 or generating triage reports.7metadata:8 source: https://skillmd.com/skills/microsoft-foundry/triaging-issues9---1011# Issue Triage Guidance1213Gather open issues and PRs, analyze them, and recommend next steps. Search the codebase to identify affected components — don't rely on hardcoded file mappings.1415## Priority Definitions1617| Priority | Criteria |18|----------|----------|19| 🔴 **Critical** | Production broken, security issue, data loss |20| 🟠 **High** | Major feature broken, blocking users |21| 🟡 **Medium** | Feature degraded, workaround exists |22| 🟢 **Low** | Minor issue, cosmetic, nice-to-have |2324## Complexity Scale2526| Size | Estimate |27|------|----------|28| **S** | Hours |29| **M** | 1-2 days |30| **L** | 3-5 days |31| **XL** | 1+ week |3233## Label Taxonomy3435| Prefix | Values |36|--------|--------|37| `area:` | `backend`, `frontend`, `auth`, `streaming`, `infra`, `docs` |38| `type:` | `bug`, `feature`, `enhancement`, `chore`, `docs` |39| `priority:` | `critical`, `high`, `medium`, `low` |4041## Triage Report Format4243### Open Issues Summary4445| # | Title | Priority | Type | Complexity |46|---|-------|----------|------|------------|4748### Per Issue — #[number]: [title]4950- **Priority** / **Type** / **Complexity**51- **Affected Areas**: checklist of areas52- **Relevant Files**: table with file + reason53- **Suggested Labels**: using taxonomy above54- **Recommended Next Steps**: numbered list5556### Open PRs Summary5758| # | Title | Author | Status | Files Changed |59|---|-------|--------|--------|---------------|6061### Per PR — #[number]: [title]6263- **Status**: Draft | Ready for review | Changes requested | Approved64- **Review Notes**: concerns or things to check6566## gh CLI Commands for Read-Only Analysis6768```bash69# List open issues70gh issue list --state open7172# Search for potential duplicates73gh issue list --search "keyword"7475# View issue details76gh issue view <number>7778# List open PRs79gh pr list --state open8081# View PR details and diff82gh pr view <number>83gh pr diff <number>84```8586## Duplicate Detection8788Before deep-diving into an issue, search for duplicates:89901. Use `gh issue list --search "<keywords>"` with key terms from the issue title and body.912. Check closed issues too: `gh issue list --state closed --search "<keywords>"`.923. If a duplicate exists, note it in the triage report with a cross-reference.9394## Constraints9596- ❌ **Read-only** — do NOT modify issues or PRs97- ❌ No `gh issue edit`, `gh issue close`, `gh issue label`98- ❌ No `gh pr merge`, `gh pr close`, `gh pr review --approve`99- ✅ Only use read commands: `list`, `view`, `search`, `diff`