원클릭으로
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.