메뉴
Runtime error investigation specialist. Use when diagnosing failures in running systems — parsing logs, stack traces, and production errors. NOT for code review; use silent-failure-hunter to catch swallowed exceptions at write time.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/kumaran-is/claude-code-onboarding --skill error-detective명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Root-cause-first debugging methodology for any bug, test failure, exception, or unexpected behavior — mandates investigation before proposing fixes. Use when something is broken, not working, crashing, or throwing errors; triggers: debug, error, bug, exception, stack trace, not working, crash.
Browser automation and testing using playwright-cli (stateful Bash CLI for scripted tests — network inspection, console monitoring, screenshots, tracing) and Browser-Use MCP (autonomous agent flows). Use when the user needs to test web apps, debug browser issues, analyze performance, fill forms, run E2E user flows, or inspect network/console activity.
Use when working through a specific problem or decision using a single reasoning framework applied deeply and interactively. Covers First Principles (break assumptions, rebuild from truth), Inversion (guarantee failure, then flip), Regret Minimization (decide from age 80), and Opportunity Cost (make tradeoffs visible). Triggers: "first principles", "inversion", "regret minimization", "opportunity cost", "help me think through", "challenge my assumptions", "what am I giving up", "work backwards from failure", "what would I regret".
| name | error-detective |
| description | Runtime error investigation specialist. Use when diagnosing failures in running systems — parsing logs, stack traces, and production errors. NOT for code review; use silent-failure-hunter to catch swallowed exceptions at write time. |
| allowed-tools | Read, Grep, Glob, Bash |
| agent | error-detective |
| context | fork |
| metadata | {"triggers":"error in logs, stack trace, production error, investigate failure, log analysis, runtime error, exception in prod, service crash","related-skills":"systematic-debugging, silent-failure-hunter","domain":"quality","role":"specialist","scope":"investigation","output-format":"report"} |
| last-reviewed | 2026-03-16 |
Iron Law: Never state a root cause without log evidence at file:line — hypothesis and confirmed cause are different things.
Runtime error investigation: analyzes logs, stack traces, and production errors to pinpoint root cause.
Distinct from silent-failure-hunter:
silent-failure-hunter -> preventive, reviews source code for swallowed exceptions at write timeerror-detective -> investigative, analyzes runtime logs and stack traces after errors occur-C 5 lines)| Stack | Error pattern to grep |
|---|---|
| Spring Boot | '"level":"ERROR"' |
| NestJS | 'ERROR \[.*\]' |
| Python/FastAPI | '^ERROR:' |
| Flutter/Dart | '\[ERROR:' |
ERROR INVESTIGATION REPORT
SUMMARY:
- Error type: [exception class / HTTP status]
- Frequency: [N occurrences / hour]
- Affected services: [list]
ROOT CAUSE HYPOTHESIS (ranked):
1. [85%] [Hypothesis] — evidence: [log line]
2. [30%] [Hypothesis] — evidence: [log line]
RECOMMENDED ACTION: [specific next step]