analyze

# Code Analysis $ARGUMENTS Analyze code quality, complexity, and patterns. ## Usage ``` /analyze [path] [--type=<type>] ``` ## What This Command Does 1. **Scans** codebase or specific path 2. **Analyzes** code quality metrics 3. **Identifies** patterns and anti-patterns 4. **Reports** findings with recommendations ## Analysis Types | Type | Description | |------|-------------| | `quality` | Code quality metrics (default) | | `security` | Security vulnerability scan | | `complexity` | Cyclomatic complexity | | `dependencies` | Dependency analysis | | `coverage` | Test coverage gaps | ## Output Format ```markdown ## Code Analysis Report ### Summary - **Files Analyzed**: [count] - **Issues Found**: [count] - **Quality Score**: [score]/100 ### Metrics | Metric | Value | Threshold | |--------|-------|-----------| | Complexity | [avg] | <10 | | Duplication | [%] | <5% | | Coverage | [%] | >70% | ### Issues by Severity - Critical: [count] - High: [count] - Medium: [count] - Low: [count] ### Top Issues 1. **[Issue]** - [file:line] - [Description] - Fix: [Recommendation] ### Patterns Detected - [Pattern 1]: [locations] - [Pattern 2]: [locations] ### Recommendations 1. [Recommendation with priority] ``` ## Automated Complexity Analysis Run the bundled script for a quick complexity report: ```bash python3 ${CLAUDE_SKILL_DIR}/scripts/complexity.py . ``` Reports file counts by type, largest files, TODO/FIXME counts, and total code lines. ## Common Rationalizatio...