analyze-code-structure
Examine code organization and identify structural patterns. Use when reviewing module design.
Best use case
analyze-code-structure is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Examine code organization and identify structural patterns. Use when reviewing module design.
Teams using analyze-code-structure should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/analyze-code-structure/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analyze-code-structure Compares
| Feature / Agent | analyze-code-structure | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Examine code organization and identify structural patterns. Use when reviewing module design.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Analyze Code Structure Examine code organization, module hierarchy, and structural patterns to understand how components are organized. ## When to Use - Initial codebase review and orientation - Understanding existing module organization - Identifying code structure for documentation - Planning refactoring or reorganization ## Quick Reference ```bash # Quick code structure analysis find . -name "*.py" -o -name "*.mojo" | head -20 tree -L 2 --dirsfirst grep -r "^class\|^def\|^fn\|^struct" --include="*.py" --include="*.mojo" | head -30 ``` ## Workflow 1. **Survey the codebase**: Identify top-level modules and packages 2. **Map module hierarchy**: Create visual tree of module organization 3. **List main components**: Classes, structs, major functions 4. **Trace imports**: Understand module dependencies 5. **Document findings**: Summarize structure for team ## Output Format Structure analysis: - Module/package hierarchy (tree view) - Key components per module - Import dependencies - Layer organization (if applicable) - Notable patterns (MVC, singleton, factory, etc.) ## References - See `analyze-code-structure` tier-2 skill for deeper analysis - See CLAUDE.md > Modularity for design principles - See `identify-architecture` skill for ML-specific structure
Related Skills
analyze-rust-optimizations
This skill performs thorough analysis of Rust libraries to find optimization opportunities. It should be used when reviewing Rust code for performance improvements, memory efficiency, or when profiling indicates bottlenecks. Focuses on runtime performance and memory usage through dynamic profiling tools and static code analysis.
analyze-project-architecture
LLM-based architectural analysis that transforms raw project data into meaningful structure
analyze-pr-performance
Analyze code review pipeline performance for a specific PR. Use when investigating slow PRs, identifying bottlenecks, or debugging performance issues in code reviews.
analyze
Deep analysis and investigation
analyze-m1-module-for-migration
Systematically analyze a Magento 1 module to determine its purpose, usage, and migration requirements for Magento 2. Use when you need to decide whether to migrate a M1 module, find alternatives, or skip it.
analyze-function
Deep line-by-line analysis of a function or method. Explains what each line does, why it's written that way, performance implications, edge cases, and design patterns. Use when user says "analyze-function", "analyze {function}", "deep dive on {function}", or "explain {function} line by line".
analyze-friction
Orchestrate 3-stage friction analysis workflow across conversations. Extracts raw friction, abstracts patterns, and presents for approval. Use when user wants to analyze conversation history for improvement opportunities.
analyze-codebase
Analyze a codebase to generate a comprehensive architecture and structure report. Use when user wants to understand a codebase, explore project structure, or generate analysis.
analyze-code
Deep code analysis using consultant agent. Identifies technical debt, risks, and improvement opportunities.
analyze-architecture
Comprehensive brownfield architecture analysis for existing codebases. Discovers structure, identifies patterns, assesses quality, calculates production readiness, and provides actionable recommendations. Use when analyzing existing codebases to understand architecture, assess quality, or prepare for modernization.
agentic-structure
Collaborative programming framework for production-ready development. Use when starting features, writing code, handling security/errors, adding comments, discussing requirements, or encountering knowledge gaps. Applies to all development tasks for clear, safe, maintainable code.
acc-analyze-solid-violations
Analyzes PHP codebase for SOLID principle violations. Detects God classes (SRP), type switches (OCP), broken contracts (LSP), fat interfaces (ISP), and concrete dependencies (DIP). Generates actionable reports with severity levels and remediation recommendations.