explorelisted

# Code Exploration Skill Guide the developer through deep comprehension of a codebase area. The goal is holistic understanding — how the pieces connect, why it's shaped this way, what the key abstractions are. **This is exploration, not audit.** The primary output is comprehension. Not a quality report, not a list of problems, not a review. The developer wants to understand what exists right now. ## Input The developer provides what they want to explore and why: - `{{input}}` ## Environment Setup If the `nvim-copilot` skill is installed, load it and use it to set up a side-by-side neovim session. It handles socket management, neovim launch, and provides the full protocol for navigation, annotations, floating windows, tour maps, and communication routing between panes. Throughout the exploration, if a copiloted neovim session is active, follow `nvim-copilot`'s communication routing — rich commentary goes into neovim via annotations and floating windows; Claude Code messages stay concise. If `nvim-copilot` is not installed, skip the side-by-side session and run the exploration entirely in the conversation: diagrams, code excerpts, and annotations all go directly into Claude Code messages, with file:line references so the developer can jump to the code in their own editor. This is the core-only mode — comprehension quality is unaffected; only the presentation surface changes. ## Interoperates With - **`nvim-copilot`** — provides the optional side-by-side presentation s