Code Analyzer

What it does

The Code Analyzer skill performs static code analysis and calculates various metrics to identify potential bugs, vulnerabilities, and style issues within your codebase. It leverages a tool called analyzer.mjs which runs automatically from the project root. The goal is to improve development efficiency and overall code quality by highlighting areas needing attention.

When to use it

• Before refactoring: Analyze code before making significant changes to understand its structure and potential impact.
• During code review: Identify complex or problematic sections for reviewers to focus on.
• As part of a CI/CD pipeline: Integrate the analyzer into your automated build process to catch issues early (using project-analyzer/doctor for health checks).
• To track code quality trends: Monitor metrics over time to identify areas where code is degrading or improving.

Key capabilities

• Project-wide analysis: Analyzes the entire project codebase.
• File-specific analysis: Allows analyzing a single file.
• Complexity calculation: Calculates cyclomatic complexity, lines of code (LOC), maintainability index, and identifies duplicate blocks.
• Hotspot identification: Pinpoints areas with high complexity for focused review.
• Trend analysis: Tracks metric trends over time to monitor code quality changes.
• Integration with other agents: Works well with code-reviewer, refactoring-specialist, and architect AI agent roles.

Example prompts

• "Analyze the entire project for complexity hotspots."
• "Can you summarize the analysis of this file?" (followed by providing a filename)
• "Show me the trends in cyclomatic complexity over the last week."

Tips & gotchas

• Node.js Requirement: Ensure Node.js version 18 or higher is installed before using the skill.
• Start Broad, Then Focus: Always run project-wide analysis before drilling down into individual files for best results.
• Prioritize Churn: When identifying hotspots, prioritize files with both high complexity and frequent changes (high churn).