project-context-analyzer
Analyzes project structure, dependencies, and patterns to generate comprehensive context documentation. Uses parallel agent execution for faster analysis. Helps understand unfamiliar codebases quickly.
When & Why to Use This Skill
The Project Context Analyzer is a high-performance Claude skill designed to automate the mapping and documentation of complex codebases. By leveraging parallel agent execution (swarm intelligence), it rapidly identifies project structures, frameworks, and dependencies, providing developers and AI agents with the essential architectural context needed for efficient coding, debugging, and seamless onboarding.
Use Cases
- Rapid Developer Onboarding: Automatically generate a comprehensive overview of unfamiliar repositories, including entry points and directory structures, to reduce the learning curve for new team members.
- AI Context Optimization: Create and maintain a '.project-context.md' file that serves as a high-quality knowledge base for other AI agents, significantly improving the relevance and accuracy of AI-generated code.
- Automated Technical Audits: Quickly detect project frameworks (e.g., React, Vite, Python) and analyze dependency trees to identify the tech stack and potential architectural bottlenecks.
- Documentation as Code: Streamline the maintenance of project documentation by generating up-to-date architectural maps and pattern analysis without manual intervention.
- Cross-Language Analysis: Seamlessly switch between JavaScript, TypeScript, and Python projects to extract consistent structural insights across polyglot codebases.
| name | Project Context Analyzer |
|---|---|
| description | Analyzes project structure, dependencies, and patterns to generate comprehensive context documentation. Uses parallel agent execution for faster analysis. Helps understand unfamiliar codebases quickly. |
| trigger | both |
Purpose
Analyze a project's structure, dependencies, framework, and patterns to generate comprehensive context documentation. Uses parallel agent swarm execution for blazing-fast analysis. Helps with onboarding, understanding unfamiliar codebases, and providing context to other AI agents. Uses specialized analysis tools for deep project understanding.
Variables
ENABLE_JAVASCRIPT: true # Enable JavaScript/TypeScript project analysis ENABLE_PYTHON: true # Enable Python project analysis ENABLE_GO: false # Enable Go project analysis (not yet implemented) ENABLE_PARALLEL_EXECUTION: true # Use parallel agent swarm for faster analysis OUTPUT_MODE: display # Options: display (show results), save (write to file) OUTPUT_FILE: .project-context.md # Where to save report if OUTPUT_MODE is save SUPPORTED_PROJECT_TYPES: javascript, typescript, python # Currently supported project types
Workflow
Parse User Request
- Determine intent: analyze, generate, show project context
- Determine output mode: display or save
- Display mode triggers: "analyze project", "show me project context", "what is this project"
- Save mode triggers: "generate project context and save", "save project context"
- Example: "analyze this project" → Intent: analyze, Mode: display
Detect Project Type
- Tool: Run
tools/detect_framework.py - Checks for: package.json (JS/TS), requirements.txt/pyproject.toml (Python), go.mod (Go)
- Returns: {type, framework, language, confidence}
- Example: package.json found → {type: "nodejs", framework: "react-vite", language: "typescript", confidence: "high"}
- Tool: Run
Route to Cookbook
- Based on detected type and ENABLE flags
- JavaScript/TypeScript: IF package.json AND ENABLE_JAVASCRIPT → javascript.md
- Python: IF requirements.txt/pyproject.toml AND ENABLE_PYTHON → python.md
- Unknown: IF no match → Basic analysis with Glob/Read
- Example: TypeScript project detected + ENABLE_JAVASCRIPT=true → Route to cookbook/javascript.md
Execute Analysis Tools
- IF: ENABLE_PARALLEL_EXECUTION is true → Launch parallel agent swarm for analysis tasks
- Tools in
tools/directory perform specialized analysis - Tool: Task with run_in_background: true for each analysis task
- Agents: DependencyAnalyzer, StructureMapper, EntryPointFinder run simultaneously
- Common tools: detect_framework, analyze_dependencies, analyze_structure, find_entry_points
- Example: JavaScript project → Launch 3 parallel agents (dependencies, structure, entry points) → All complete in ~4s vs ~9s sequential
Aggregate Results
- IF parallel execution used → Collect all agent results using TaskOutput
- Combine data from all analysis tools
- Generate formatted report with sections: overview, structure, dependencies, entry points
- Keep comprehensive but concise (focus on what's important)
- Example: Collect swarm results → Combine framework info + dependencies + structure → Complete context document with performance metrics
Output Report
- IF OUTPUT_MODE is "display" OR user requested display: Show results in chat
- IF OUTPUT_MODE is "save" OR user requested save: Write to OUTPUT_FILE
- Example: "show me context" → Display in chat, "generate and save" → Write to .project-context.md
Cookbook
JavaScript/TypeScript Projects
- IF: The project has a
package.jsonfile ANDENABLE_JAVASCRIPTis true. - THEN: Read and execute:
.claude/skills/project-context/cookbook/javascript.md
Python Projects
- IF: The project has
requirements.txtorpyproject.tomlANDENABLE_PYTHONis true. - THEN: Read and execute:
.claude/skills/project-context/cookbook/python.md
Unknown Project Type
- IF: No specific project type detected.
- THEN: Perform basic analysis using available built-in tools (Glob, Read).
- Report what can be detected and suggest adding Go or other language support.