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: Provides issue triage workflow, priority definitions, and report format. Use when analyzing GitHub issues and PRs, assessing priority, or generating triage reports.4---56# Issue Triage Guidance78Gather open issues and PRs, analyze them, and recommend next steps. Search the codebase to identify affected components — don't rely on hardcoded file mappings.910## Priority Definitions1112| Priority | Criteria |13|----------|----------|14| 🔴 **Critical** | Production broken, security issue, data loss |15| 🟠 **High** | Major feature broken, blocking users |16| 🟡 **Medium** | Feature degraded, workaround exists |17| 🟢 **Low** | Minor issue, cosmetic, nice-to-have |1819## Complexity Scale2021| Size | Estimate |22|------|----------|23| **S** | Hours |24| **M** | 1-2 days |25| **L** | 3-5 days |26| **XL** | 1+ week |2728## Label Taxonomy2930| Prefix | Values |31|--------|--------|32| `area:` | `backend`, `frontend`, `auth`, `streaming`, `infra`, `docs` |33| `type:` | `bug`, `feature`, `enhancement`, `chore`, `docs` |34| `priority:` | `critical`, `high`, `medium`, `low` |3536## Triage Report Format3738### Open Issues Summary3940| # | Title | Priority | Type | Complexity |41|---|-------|----------|------|------------|4243### Per Issue — #[number]: [title]4445- **Priority** / **Type** / **Complexity**46- **Affected Areas**: checklist of areas47- **Relevant Files**: table with file + reason48- **Suggested Labels**: using taxonomy above49- **Recommended Next Steps**: numbered list5051### Open PRs Summary5253| # | Title | Author | Status | Files Changed |54|---|-------|--------|--------|---------------|5556### Per PR — #[number]: [title]5758- **Status**: Draft | Ready for review | Changes requested | Approved59- **Review Notes**: concerns or things to check6061## gh CLI Commands for Read-Only Analysis6263```bash64# List open issues65gh issue list --state open6667# Search for potential duplicates68gh issue list --search "keyword"6970# View issue details71gh issue view <number>7273# List open PRs74gh pr list --state open7576# View PR details and diff77gh pr view <number>78gh pr diff <number>79```8081## Duplicate Detection8283Before deep-diving into an issue, search for duplicates:84851. Use `gh issue list --search "<keywords>"` with key terms from the issue title and body.862. Check closed issues too: `gh issue list --state closed --search "<keywords>"`.873. If a duplicate exists, note it in the triage report with a cross-reference.8889## Constraints9091- ❌ **Read-only** — do NOT modify issues or PRs92- ❌ No `gh issue edit`, `gh issue close`, `gh issue label`93- ❌ No `gh pr merge`, `gh pr close`, `gh pr review --approve`94- ✅ Only use read commands: `list`, `view`, `search`, `diff`
microsoft-foundry