# Debug Specialist

> 디버깅, 디버그, 버그, 에러, 오류, 버그 수정, 원인 분석, 로그 분석, 트러블슈팅, 문제 해결 - Identifies root causes of runtime bugs, analyzes error logs, and provides robust fixes. Use when user reports errors, unexpected behavior, or performance issues at runtime. Do NOT use for build/compilation errors (use build-error-resolver) or code quality issues (use code-reviewer).

- Skill: `aimskr/debug-specialist` (Agent Skill)
- Install (CLI): `npx skillmds@latest add aimskr/debug-specialist`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aimskr/debug-specialist/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: aimskr (https://skillmd.com/u/aimskr)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/aimskr/debug-specialist

---


# Debug Specialist Workflow

## Core Principles
1. **Reproduce First**: Never attempt a fix without understanding how to trigger the bug.
2. **Scientific Method**: Formulate a hypothesis, test it, and verify the results.
3. **Root Cause Analysis**: Don't just patch the symptom; fix the underlying issue.
4. **Regression Testing**: Ensure the fix doesn't break existing functionality.

## Process
1. **Context Gathering**: 
   - Request error logs, stack traces, or screenshots.
   - Ask about the environment and recent changes.
2. **Analysis**:
   - Trace the execution flow leading to the error.
   - Identify edge cases or race conditions.
3. **Fixing**:
   - Propose the most robust solution.
   - Explain *why* the bug occurred.
4. **Verification**:
   - Run tests to confirm the fix works.
   - Check for side effects.

## 문서화 (작업 완료 후 자동 실행)

버그 수정 완료 시 `auto-documenter`를 호출하여 프로젝트 문서를 업데이트한다.
전달 정보: 버그 원인, 수정 파일 목록, 영향 범위.

## Completion

버그 수정 + 테스트 통과 + 회귀 없음이 확인되면 완료.

## Troubleshooting

**Bug is not reproducible**: Gather environment details (OS, runtime version, config). Check for race conditions or timing-dependent behavior. Add logging to narrow down the trigger.
**Fix works locally but not in CI/production**: Environment diff is the likely cause. Compare env vars, dependency versions, and runtime configs between environments.
**Multiple bugs interleaved**: Isolate each bug with a separate test case. Fix one at a time, verify after each fix. Never batch-fix without individual verification.