explore
Read-only codebase investigation via Explore agent; also handles upward-zoom for unfamiliar code regions. Triggers "how does X work", "where is X", "find X", "understand X", "navigate codebase", "zoom out", "bigger picture", "where does this fit".
适合你，如果想快速弄清陌生代码库的来龙去脉
npx oh-my-skill add darkroomengineering/cc-settings/explorecurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- darkroomengineering/cc-settings/explorenpx oh-my-skill verify darkroomengineering/cc-settings/explore怎么用
商店整理自技能原文 · 版本 fa04efc · 表述以原文为准装上后，Claude 会启动只读的 Explore agent 调查代码。它不修改文件，而是根据你的问题选择两种模式：广域调查（从全局找起）或向上缩放（聚焦已知代码看它如何融入系统），最后返回文件位置、流程解释等总结。
当你询问“某个功能如何工作”、“某段代码在哪里”，或者要求“看整体结构”、“这个模块怎么融入系统”时触发。
技能原文 SKILL.md
Codebase Exploration
Delegates to the Explore agent for fast, read-only investigation of the codebase.
Current State
- Directory: !
pwd 2>/dev/null - Project: !
basename "$(pwd)" 2>/dev/null - Stack: !
ls package.json Cargo.toml go.mod pyproject.toml 2>/dev/null || echo "unknown" - Git root: !
git rev-parse --show-toplevel 2>/dev/null || echo "not a git repo"
Two modes — pick by what the user asked
Broad investigation mode (default)
Use when the user is asking "how does X work" / "where is X" / "what handles Y" — finding code without a known starting point.
- Start broad - Use
tldr semanticorGlobto find relevant files - Narrow down - Read specific files to understand implementation
- Trace connections - Use
tldr impactto find callers/dependencies - Summarize findings - Return clear, actionable summary
Upward-zoom mode
Use when the user is staring at a known function or module and needs to know how it fits — triggers like "zoom out", "bigger picture", "where does this fit", onboarding unfamiliar code.
- Follow [../context-doc/DOMAIN-AWARENESS.md](../context-doc/DOMAIN-AWARENESS.md) — read
CONTEXT.mdand any relevant ADRs first if they exist. - Identify the symbol or file the user is asking about.
- Use TLDR for the structural answer:
``bash tldr context <symbol> --depth 3 --project . tldr impact <symbol> --project . ``
- Synthesize a map: list immediate callers, the modules they live in, and where this area sits in the system. Use
CONTEXT.mdvocabulary when naming concepts. - Stop at one layer up. The user can ask for another zoom-out if they need it.
Upward-zoom output shape:
{Symbol/file in question}
↑ called by: {module A}, {module B}
↓ depends on: {module C}, {module D}
Where this fits:
{1–2 sentence narrative using CONTEXT.md terms}
Related ADRs:
- ADR-NNNN ({title}) — relevant because…
The point is orientation, not exhaustive coverage.
Output Format (broad mode)
Return a concise summary:
- Location: Key files and their paths
- How it works: Brief explanation of the flow
- Key functions/components: Entry points
- Dependencies: What it relies on
- Suggestions: If the user needs to modify something
Remember
- You are READ-ONLY - do not modify files
- Return summaries, not raw file contents
- Be specific with file paths and line numbers