Menu
Review new GitHub issues, assess priority and urgency, suggest labels, and recommend assignees
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Generate Mermaid architecture diagrams showing system components, layers, and data flows
Proactively identify at-risk issues and PRs: stale items, blocked work, deadline risks, scope creep, and unassigned high-priority items
Extract common questions from closed GitHub issues and generate an FAQ document with answers
Search project notes by topic, synthesize findings into a consolidated summary with cross-references
Proactively identify information gaps in project context and generate actionable questions to surface missing requirements, unclear specifications, or documentation gaps
Generate Mermaid dependency graphs showing issue relationships, blocking chains, and critical paths
| name | triage-new-issues |
| description | Review new GitHub issues, assess priority and urgency, suggest labels, and recommend assignees |
| instructions | When triaging new GitHub issues, assessing priority and urgency, suggesting labels, or recommending assignees |
| tags | ["triage","issues","priority","labels","backlog"] |
Review new or untriaged GitHub issues, assess priority based on urgency signals, suggest labels, and recommend owners.
Activate when:
## Triage: #[number] — [title]
### Priority Assessment
**Urgency**: [Critical | High | Medium | Low]
**Impact**: [Wide | Moderate | Limited]
**Recommended Priority**: P[0-3]
| Signal | Indicator |
|--------|-----------|
| [Keyword/label found] | [What it suggests] |
### Classification
**Type**: [Bug | Feature | Question | Task]
**Area**: [Component or area affected]
**Suggested Labels**: `priority/high`, `bug`, `area/auth`
**Suggested Assignee**: @username (owns this area)
### Assessment
[Summary of the issue and reasoning for priority assignment]
### Clarifying Questions (if needed)
- [ ] [Question to understand severity]
### Recommendation
[Immediate action | Next sprint | Backlog | Needs info | Duplicate of #X]
Keywords: "down", "outage", "security", "vulnerability", "production", "urgent", "ASAP", "breach"
Labels: critical, security, production
Action: Immediate attention required
Keywords: "blocking", "regression", "broken", "can't use", "data loss", "crash"
Labels: blocker, regression, priority/high
Action: Address this sprint
Keywords: "bug", "incorrect", "should", "expected", "wrong"
Labels: bug, priority/medium
Action: Schedule for upcoming sprint
Keywords: "nice to have", "minor", "cosmetic", "enhancement", "workaround exists"
Labels: enhancement, low-priority
Action: Add to backlog