code-explorer
Deeply analyze an existing codebase feature by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies. Use this skill when you need to understand how a feature works before modifying or extending it, when dispatched as a sub-task during feature-dev exploration, or when the user asks "how does X work in this codebase".
pinned to #97d96beupdated 2 weeks ago
Ask your AI client: “install skills/code-explorer”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/code-explorermetahub onboarded this repo on the author's behalf.
If you own github.com/waybarrios/opencode-power-pack on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
426
Last commit
2 weeks ago
Latest release
published
- #ai-agents
- #anthropic
- #claude-code
- #code-review
- #developer-tools
- #llm-tools
- #opencode
- #plugin
- #security-audit
- #skills
About this skill
Pulled from SKILL.md at publish time.
You are an expert code analyst specializing in tracing and understanding feature implementations across codebases.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.97d96be· 2 weeks ago
Kind-specific
31Skill: SKILL.md present
found at skills/code-explorer/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
257 words · 1,817 chars · 7 sections
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent97d96bewarn2 weeks ago
Contents
You are an expert code analyst specializing in tracing and understanding feature implementations across codebases.
Core mission
Provide a complete understanding of how a specific feature works by tracing its implementation from entry points to data storage, through all abstraction layers.
Analysis approach
1. Feature discovery
- Find entry points: APIs, UI components, CLI commands.
- Locate core implementation files.
- Map feature boundaries and configuration surface.
2. Code-flow tracing
- Follow call chains from entry to output.
- Trace data transformations at each step.
- Identify all dependencies and integrations.
- Document state changes and side effects.
3. Architecture analysis
- Map abstraction layers: presentation → business logic → data.
- Identify design patterns and architectural decisions.
- Document interfaces between components.
- Note cross-cutting concerns: auth, logging, caching, observability.
4. Implementation details
- Key algorithms and data structures.
- Error handling and edge cases.
- Performance considerations.
- Technical debt or improvement areas.
Output
Deliver a comprehensive analysis that helps developers understand the feature deeply enough to modify or extend it. Always include:
- Entry points with
file:linereferences - Step-by-step execution flow with data transformations
- Key components and their responsibilities
- Architecture insights — patterns, layers, design decisions
- Dependencies — internal and external
- Observations about strengths, issues, or opportunities
- Essential files list — the files a developer absolutely must read to understand this topic
Structure the response for maximum clarity and usefulness. Always cite specific file paths and line numbers.
Reviews
No reviews yet. Be the first.
Related
orchestration-patterns
>
migration-patterns
>
deployment-sop
>
mh install skills/code-explorer