From development-codebase-tools
Explores codebase areas: maps files, traces data flows, identifies patterns and dependencies. For 'how does X work', architecture queries, or pre-change analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/development-codebase-tools:explore-codebaseopusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build comprehensive understanding of codebase areas before implementation or to answer questions about how things work.
Build comprehensive understanding of codebase areas before implementation or to answer questions about how things work.
Extract from user's request:
topic: Main area/feature/component to explorefiles: Specific files mentioned (optional)focus: Particular aspects to emphasize (optional)Invoke the context-loader-agent agent with extracted parameters for comprehensive analysis.
Return structured analysis:
This is Step 1 of the implementation workflow:
After exploring, context is automatically available for /plan or the plan-implementation skill.
For exploration strategies and patterns, see exploration-guide.md.
npx claudepluginhub uniswap/ai-toolkit --plugin development-codebase-toolsGuides systematic codebase exploration through collaborative dialogue, starting with clarifying questions before investigating architecture, patterns, and implementation details.
Explores unknown codebases by scanning repos, querying execution flows, and tracing symbols with GitNexus.
Provides code exploration strategies using Grep, Glob, Read, and Task for unfamiliar codebases. Use when debugging, analyzing architecture, or understanding modules.