メニュー
Use when a bug report, error message, alert, or issue needs classification, deduplication, severity, ownership, refinement, and reusable triage learning before implementation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when debugging a failing test, broken build, runtime error, or unexpected system behavior. Drives hypothesis-based investigation, root-cause fixes, verification, and reusable learning capture.
Use when a claim, plan, spec, doc, or design must be attacked against source evidence before implementation or approval. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when fixing broken behavior and the priority is reproduce, root cause, regression proof, and the smallest safe repair. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when reviewing code changes with explicit stage, target, and focus so own-code checks and others’ PR reviews stay distinct but share one contract. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when the deliverable is docs or reference material and every claim must stay tied to observed behavior or cited source evidence. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when adding or changing product behavior that must ship with explicit purpose, scenarios, and verification. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
| name | issue-triage |
| description | Use when a bug report, error message, alert, or issue needs classification, deduplication, severity, ownership, refinement, and reusable triage learning before implementation. |
Use this skill when:
Do not use when the issue is already labeled, assigned, deduplicated, and actionable. Do not use to fix the bug.
Triage is classification, not solution. Answer: Is this real? Is this known? Who should fix it?
Duplicate: <none | issue link>
Severity: <P0 | P1 | P2 | P3> because <impact>
Component: <area>
Owner: <team/person | unknown>
Missing Info: <none | requested detail>
Next Action: <diagnose | close | wait for info | route>
Use canonical/learning-template.md when triage reveals a reusable classification rule, ownership rule, severity trap, or routing pattern.
Raw triage learnings go to specs/memory/sessions/learning-YYYY-MM-DD-<slug>.md. Durable promotion requires memory-promotion approval.
diagnose — debug after triage.task-to-issues — create issues from unstructured text.memory-promotion — promote reusable triage knowledge.