From ai-debugger
Use when tracing code paths related to an API issue - explores both source code and docs/ to find root cause, referencing business rules and architecture docs alongside implementation
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-debugger:code-exploreThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
코드베이스와 docs/를 함께 탐색하여 이슈 관련 로직을 추적한다.
코드베이스와 docs/를 함께 탐색하여 이슈 관련 로직을 추적한다.
Controller → UseCase/Service → Repository/Client 순으로 추적:
코드 분석과 병행하여:
docs/policies/ — 비즈니스 규칙이 코드에 올바르게 반영되었는지docs/architecture/ — 설계 의도와 실제 구현의 불일치CLAUDE.md — 프로젝트 컨벤션 위반 여부=== Code Analysis ===
Entry: OrderController.createOrder (order/app/.../controller/OrderController.kt:45)
Flow: CreateOrderUseCase → OrderService.create → OrderRepository.save
Suspect: OrderService.kt:89 - 재고 차감 로직에서 동시성 미처리
docs/policies/inventory-rules.md:
"재고 차감은 비관적 락으로 처리해야 함" — 코드에 락 미적용
Verdict: 코드 이슈 (동시성 처리 누락)
npx claudepluginhub 1989v/ai --plugin ai-debuggerInvestigates code by tracing execution paths, mapping data flow, and diagnosing root causes. Outputs an analysis report with architecture overview and findings.
Deep-dive into a codebase question, failure, or architectural concern without making changes
Explains, traces, audits, or explores code in read-only mode without modifying it. Answers questions like 'how does X work' or 'where is Y called' with evidence.