Agent skill
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).
Install this agent skill to your Project
npx add-skill https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/debug-specialist
Metadata
Additional technical details for this skill
- author
- jaehashin
- version
- 1.2.0
SKILL.md
Debug Specialist Workflow
Core Principles
- Reproduce First: Never attempt a fix without understanding how to trigger the bug.
- Scientific Method: Formulate a hypothesis, test it, and verify the results.
- Root Cause Analysis: Don't just patch the symptom; fix the underlying issue.
- Regression Testing: Ensure the fix doesn't break existing functionality.
Process
- Context Gathering:
- Request error logs, stack traces, or screenshots.
- Ask about the environment and recent changes.
- Analysis:
- Trace the execution flow leading to the error.
- Identify edge cases or race conditions.
- Fixing:
- Propose the most robust solution.
- Explain why the bug occurred.
- 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
build-error-resolver
빌드 에러, 빌드 오류, 컴파일 에러, 빌드 실패 해결, 의존성 에러 - Specialized in resolving build errors, compilation failures, and dependency issues. Use when build fails, compilation errors occur, or dependency conflicts arise. Do NOT use for runtime bugs or logic errors (use debug-specialist instead).
brainstorming
브레인스토밍, 아이디어, 기획, 구상, 아이디어회의, 설계, 요구사항 분석, 접근법 탐색 - Use before creating new features or significant changes to explore user intent, requirements, and design options. Collaborative brainstorming through step-by-step questioning. Do NOT use for simple bug fixes, config changes, or tasks with clear requirements already defined.
doc-coauthoring
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서, RFC, 설계 문서, 의사결정 문서 - Collaborative document co-authoring through 3 stages: context gathering, iterative refinement, and reader testing. Use when writing docs, proposals, tech specs, decision docs, or RFCs. Do NOT use for PRD/product requirements (use prd-strategist) or implementation plans (use writing-plans).
testing-strategy
테스트 전략, 테스팅 계획, QA 전략, 품질 보증, 테스트 피라미드, 테스트 시나리오, 커버리지 목표 - Designs test strategies including test pyramid ratios, scenario categories, and coverage targets. Use when planning how to test a feature, designing QA approach, or creating test plans. Do NOT use for TDD implementation (use tdd-workflow) or E2E test execution (use e2e-runner).
learning-research
학습 리서치, 학습 자료, 공부 자료, 학습, 공부, 스터디, 개념 정리, 이해 - 특정 주제를 깊이 이해하기 위한 학습 자료를 수집·정리한다. 병렬 전문가 서브에이전트로 개념, 원리, 실습, 심화 자료를 수집하고 이해도별로 체계화된 학습 노트를 생성한다. Obsidian vault에 자동 저장. 의사결정용 자료 조사는 research 스킬을, 시장조사는 market-research 스킬을 사용할 것.
devil-advocate
Didn't find tool you were looking for?