メニュー
Use when processing new or untriaged GitHub issues - assesses urgency from keyword and label signals, assigns P0-P3 priority, suggests labels and assignees, and flags issues needing escalation or clarification
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | triage-new-issues |
| description | Use when processing new or untriaged GitHub issues - assesses urgency from keyword and label signals, assigns P0-P3 priority, suggests labels and assignees, and flags issues needing escalation or clarification |
Review new or untriaged GitHub issues, assess priority based on urgency signals, suggest labels, and recommend owners.
Activate when:
Use the gh CLI (must be installed and authenticated):
# Find untriaged issues
gh issue list --search 'no:label' --json number,title,body,labels
# Apply labels after triage
gh issue edit <n> --add-label <label>
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
git log on affected paths, or past assignees of similar issues — omit the assignee suggestion if none found## 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 — based on CODEOWNERS, git history, or similar past issues (omit if no owner found)
### 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]
Use when setting up a new Claude Code project, when a repo has no CLAUDE.md, or when starting work on an empty codebase - interviews the user and authors a CLAUDE.md covering project purpose, tech stack, TDD rules, and development practices
Use when the user asks for an architecture diagram, says 'show me the system architecture' or 'diagram the components', or during project planning - generates GitHub-compatible Mermaid flowcharts showing components, layers, subgraph boundaries, and data flows
Use when asked about project health, stale or blocked issues, deadline risk, or scope creep - scans GitHub issues and PRs with heuristics (staleness, blocked labels, milestone dates, size, unassigned high-priority) and produces a severity-ranked at-risk report
Use when building or updating an FAQ from closed GitHub issues, documenting recurring support questions, or reducing repeat questions - extracts common questions from resolved issues and generates a categorized FAQ document with synthesized answers and source links
Use when knowledge on a topic is scattered across multiple project notes and someone asks to consolidate, synthesize, or summarize what has been documented - searches notes by topic and produces a single summary with key points, timeline, cross-references, and documentation gaps
Use when asked 'what am I missing?', reviewing an issue or draft before submission, or checking documentation completeness - detects requirement, spec, and doc gaps and generates prioritized actionable questions