issue-triage
Triage and organize GitHub issues. Triggers on: 'triage', 'triage issues', 'organize backlog'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Triage and organize GitHub issues. Triggers on: 'triage', 'triage issues', 'organize backlog'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Evaluate architectural decisions, propose ADRs. Triggers on: 'architecture review', 'ADR', 'design review'.
Perform structured code reviews. Triggers on: 'code review', 'review code', 'review PR'.
Create GitHub pull requests. Triggers on: 'create PR', 'pull request', 'submit PR'.
Evaluate strategic direction changes before execution. Triggers on: 'direction change', 'strategic decision', 'pivot'.
Create new custom agent definition. Triggers on: 'create agent', 'new agent'.
Create new instructions file. Triggers on: 'create instructions', 'new instructions'.
| name | issue-triage |
| description | Triage and organize GitHub issues. Triggers on: 'triage', 'triage issues', 'organize backlog'. |
Query and triage open GitHub issues that need attention. Identify items needing milestones, labels, priority scoring, or investigation.
# All open issues
gh issue list --state open --limit 50
# Issues without labels
gh issue list --state open --limit 50 | grep -v "priority:"
# Issues without milestones
gh issue list --state open --limit 50 --json number,title,milestone \
--jq '.[] | select(.milestone == null) | "#\(.number) \(.title)"'
# Stale issues (no activity in 30+ days)
gh issue list --state open --limit 50 --json number,title,updatedAt \
--jq '.[] | select(.updatedAt < (now - 2592000 | todate)) | "#\(.number) \(.title)"'
For each issue needing attention:
| Category | Action |
|---|---|
| Missing priority label | Score with ICE, add label |
| Missing milestone | Assign to current or next sprint |
| Stale (30+ days) | Close if irrelevant, re-prioritize if still valid |
| Needs investigation | Add needs-investigation label, comment what's unclear |
| Duplicate | Close as duplicate, link to original |
| Not actionable | Request clarification or close |
For unlabeled issues, apply ICE scoring:
| Dimension | High (3) | Medium (2) | Low (1) |
|---|---|---|---|
| Impact | Core functionality or architecture | Improves robustness or tooling | Nice-to-have |
| Confidence | Strong evidence or clear requirements | Some evidence | Speculative |
| Effort | Config-only, < 1 sprint | Minor code + testing | Multi-sprint |
Score = Impact × Confidence / Effort
priority:highpriority:mediumpriority:lowgh issue edit <NUMBER> --add-label "priority:high"
Assign labels based on priority and readiness:
| Condition | Action |
|---|---|
| High priority, clear requirements | Add status:planned, assign to milestone |
| Medium priority, needs more detail | Priority label only (stays in backlog) |
| Low priority or speculative | Priority label only (stays in backlog) |
| Needs investigation first | Add needs-investigation label |
gh issue edit N --add-label "priority:high" --add-label "status:planned"
gh issue edit N --milestone "Sprint X"
## Triage Report — [Date]
### Triaged
| # | Title | Action | Priority |
|---|-------|--------|----------|
| N | Title | Labeled / Closed / Moved | high/medium/low |
### Needs Attention
- #N: [Why it needs human input]
### Stats
- Issues triaged: N
- Labels added: N
- Issues closed: N
- Stale issues identified: N