This tool analyzes source code to identify execution flows and API interfaces, summarizing code structure for debugging.
Install
mkdir -p .claude/skills/codebase-context-extractor && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1822" && unzip -o skill.zip -d .claude/skills/codebase-context-extractor && rm skill.zipInstalls to .claude/skills/codebase-context-extractor
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.Key capabilities
- →Analyze codebase structure
- →Map dependency graphs
- →Trace execution flows
- →Extract public API interfaces
- →Generate high-level summaries
How it works
The script traverses the target directory to parse code structure and relationships based on the selected extraction mode.
Inputs & outputs
When to use codebase-context-extractor
- →Map out codebase structure for large projects
- →Extract context for a specific class or module
- →Analyze inter-file dependencies
- →Prepare codebase state for debugging
About this skill
Codebase Context Extractor Skill
Overview
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
Trigger Words
- "extract context"
- "codebase context"
- "code context"
- "analyze codebase"
- "codebase analysis"
- "code structure"
- "dependency analysis"
- "code relationships"
- "understand codebase"
- "map codebase"
When to Use This Skill
Use this skill when you need to:
- Understand the structure and organization of a large codebase
- Extract relevant context for a specific function, class, or module
- Analyze dependencies and relationships between code components
- Generate documentation or summaries of code sections
- Prepare context for code modifications or debugging
- Identify entry points and execution flows
- Map out API surfaces and public interfaces
- Understand data flow and state management
Instructions
When this skill is triggered, execute the context_extractor.py script with appropriate parameters.
Basic Usage
python /projects/workspace/codebase-context-extractor/context_extractor.py \
--target-path <path_to_codebase> \
--mode <extraction_mode> \
--output <output_file>
Extraction Modes
- full - Complete codebase analysis with all components
- targeted - Focus on specific files, functions, or classes
- dependency - Map dependencies and imports
- flow - Trace execution flows and call chains
- api - Extract public interfaces and API surfaces
- data - Analyze data structures and models
- hierarchy - Show class hierarchies and inheritance
- summary - Generate high-level overview
Parameters
--target-path(required): Path to the codebase to analyze--mode(required): Extraction mode (see above)--output(optional): Output file path (default: stdout)--focus(optional): Specific file, class, or function to focus on--depth(optional): Maximum depth for traversal (default: unlimited)--include-tests(optional): Include test files in analysis (default: false)--language(optional): Programming language (auto-detected if not specified)--format(optional): Output format (markdown, json, yaml, text) (default: markdown)--exclude(optional): Patterns to exclude (comma-separated)
Examples
- Full codebase analysis:
python context_extractor.py --target-path ./my-project --mode full --output context.md
- Targeted analysis of a specific class:
python context_extractor.py --target-path ./my-project --mode targeted --focus "UserService" --output user_service_context.md
- Dependency mapping:
python context_extractor.py --target-path ./my-project --mode dependency --format json --output dependencies.json
- Execution flow analysis:
python context_extractor.py --target-path ./my-project --mode flow --focus "main" --depth 5
Output Structure
The extractor generates structured output including:
For Full/Targeted Mode
- Project Overview: Language, structure, entry points
- File Organization: Directory structure and file purposes
- Key Components: Important classes, functions, modules
- Dependencies: External and internal dependencies
- Code Metrics: Lines of code, complexity estimates
- Context Summary: High-level understanding
For Dependency Mode
- Dependency Graph: Visual representation of dependencies
- Import Analysis: All imports and their usage
- Circular Dependencies: Detection and reporting
- Unused Dependencies: Potential cleanup targets
For Flow Mode
- Call Chains: Function call sequences
- Entry Points: Main execution paths
- Exit Points: Return and error handling
- Branch Analysis: Conditional execution paths
For API Mode
- Public Interfaces: Exported functions and classes
- API Documentation: Signatures and docstrings
- Usage Examples: How to use the API
- Versioning Info: API version and compatibility
Advanced Features
Smart Context Window Management
The extractor automatically manages context size to fit within LLM token limits:
- Prioritizes most relevant code sections
- Provides summaries for less critical parts
- Includes breadcrumb navigation for context
Multi-Language Support
Supports analysis of:
- Python
- JavaScript/TypeScript
- Java
- C#
- Go
- Rust
- C/C++
- Ruby
- PHP
- And more (extensible)
Intelligent Filtering
- Excludes generated code, build artifacts, and vendor directories
- Focuses on business logic and core functionality
- Configurable exclusion patterns
Integration with Other Tools
The context extractor output can be used with:
- Documentation generators
- Code review tools
- Refactoring assistants
- Bug tracking systems
- Development environments
Best Practices
- Start with Summary Mode: Get a high-level overview before diving deep
- Use Targeted Mode for Specific Tasks: Focus on relevant code sections
- Combine with Dependency Analysis: Understand impact of changes
- Leverage Flow Analysis for Debugging: Trace execution paths
- Regular Updates: Re-run analysis as codebase evolves
Notes
- Large codebases may take time to analyze
- Consider using depth limits for very large projects
- JSON output is best for programmatic processing
- Markdown output is best for human reading
- The tool respects .gitignore patterns by default
When not to use it
- →Analyzing binary files or non-source code artifacts
- →Projects where the tool cannot access the file system
Prerequisites
Limitations
- →Large codebases may require depth limits to complete analysis
- →Relies on file system access to the target path
How it compares
It automates the mapping of complex dependencies and call chains that would otherwise require manual code tracing.
Compared to similar skills
codebase-context-extractor side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| codebase-context-extractor (this skill) | 4 | 9mo | Review | Intermediate |
| error-handling-patterns | 35 | 2mo | No flags | Intermediate |
| investigating-code-patterns | 1 | 8mo | No flags | Beginner |
| investigate | 1 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by lofcz
View all by lofcz →You might also like
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
investigating-code-patterns
CaptainCrouton89
Systematically trace code flows, locate implementations, diagnose performance issues, and map system architecture. Use when understanding how existing systems work, researching concepts, exploring code structure, or answering "how/where/why is X implemented?" questions.
investigate
MadAppGang
Unified entry point for code investigation. Auto-routes to specialized detective based on query keywords. Use when investigation type is unclear or for general exploration.
codex-review
rymetry
|
connector-librarian
frvnkfrmchicago
>
claude
yuiseki
|