一键导入
incident
Investigate production-like failures from symptoms, logs, and reproduction steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Investigate production-like failures from symptoms, logs, and reproduction steps.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guided git commit workflow — review changes, draft message, stage, commit
Manage context pressure during large codebase work without losing critical state.
Create a pull request with structured summary and test plan
Interactive debugging — reproduce, isolate, trace, fix
Explore a codebase or directory to understand its structure and purpose
Implement a requested code change end-to-end with scoped edits and verification.
| name | incident |
| description | Investigate production-like failures from symptoms, logs, and reproduction steps. |
| when_to_use | Use when behavior is intermittent, channel-specific, timing-sensitive, or observed in logs. |
| required_tools | ["bash","symbol_search"] |
| tags | ["debug","incident"] |
| activation | {"input_patterns":["(?i)(incident|outage|logs|timeout|丢消息|超时|日志|故障)"]} |
${ARGS}
Establish exact user-visible symptoms, timestamps, affected clients, and expected behavior.
Read logs and persisted session state before changing code. Separate transport failure, runtime failure, provider failure, and rendering failure.
Create the smallest repeatable scenario. If intermittent, identify timing windows and retry boundaries.
Patch the owning layer, not the symptom. Add regression coverage or an operational check where possible.
Report root cause, fix, verification, and any remaining monitoring gap.