← ClaudeAtlas

code-explorelisted

Pure Claude code investigation. Use when: tracing execution paths, understanding architecture, diagnosing issues. Not for: dual-perspective review (use code-investigate), code review (use codex-code-review). Output: analysis report with findings.
hmj1026/dhpk · ★ 1 · Code & Development · score 75
Install: claude install-skill hmj1026/dhpk
# Code Explore Skill ## Trigger - Keywords: code explore, code investigation, research code, trace code, feature understanding, quick investigation, code exploration ## When to Use - Quickly understand how a feature works - Trace execution paths / data flow - Diagnose problem root causes - No dual confirmation needed (no Codex cross-validation) ## When NOT to Use | Scenario | Alternative | | ----------------------- | ------------------------------------- | | Need dual confirmation | `/code-investigate` (Claude + Codex) | | Git history tracking | `/git-investigate` | | System verification | `/feature-verify` | | Code review | `/codex-review-fast` | ## Workflow ``` ┌──────────────────────────────────────────────────────────┐ │ Phase 1: Locate Entry Point │ ├──────────────────────────────────────────────────────────┤ │ 1. Grep keywords -> find related files │ │ 2. Identify entry points (Controller / Service / Provider) │ │ 3. Build file list │ └──────────────────────────────────────────────────────────┘ ↓ ┌──────────────────────────────────────────────────────────┐ │ Phase 2: Trace Path │ ├──────────────────────────────────────────────────────────┤ │ 1. Start from entry point, Read