← ClaudeAtlas

explorelisted

Explore the local codebase before making changes — read code, trace dependencies, scan git history, discover tests, and audit build and tool configuration. Use as step 1 before any code change, or for 'what exists for X' investigation.
melodic-software/claude-code-plugins · ★ 4 · AI & Automation · score 76
Install: claude install-skill melodic-software/claude-code-plugins
## Pre-computed context Current branch: !`git branch --show-current 2>/dev/null || echo "unknown"` Working tree status: !`git status --porcelain 2>/dev/null | head -20 || echo "clean"` Project root: !`git rev-parse --show-toplevel 2>/dev/null || echo "unknown"` These values orient this session only. The project root is an absolute machine path — use it to resolve files while working, but never echo it into `EXPLORE.md`; the handoff artifact records relative paths (see the outcome gate below). ## Routing — context preservation first (three ways to explore) Exploration reads many files; keeping that out of the main conversation is what subagents are for. Three ways to run it, by how much context it burns and whether you need this structured workflow: - **Built-in Explore subagent — context-preserving default.** For raw "where is X / how does Y work" search, delegate to a fresh Explore subagent ("use a subagent to investigate X"). Fast, read-only, context-isolated. It skips project memory (convention-blind) and does NOT run this 6-dimension workflow or write `EXPLORE.md` — pass key constraints in the prompt when conventions matter. Scale 1→N for coverage: dispatch more Explore subagents (each owning a disjoint area) until nothing relevant to the task is left undiscovered; the main session synthesizes their summaries and persists the artifact. - **Inline `/explore` — this structured workflow, scoped.** Stay here when ALL hold: ≤~5 known files; tight turn-by-turn iteration; f