Analyze Mode
Deep analysis of your codebase — quality, security, architecture, performance, and technical debt.
Deep analysis of your codebase.
Analyze mode performs a multidimensional examination of your code and produces a structured report with findings, metrics, and recommendations. Unlike Review mode — which focuses on recent changes — Analyze looks at the full picture.
What it does
Analyze mode examines your codebase across multiple dimensions: code quality, security vulnerabilities, architectural patterns, performance concerns, and technical debt. The output is a structured report categorized by domain, with specific findings, severity levels, and actionable recommendations. The report is persisted to your Documents so you can reference it over time.
When to use it
- Auditing a codebase you've just inherited or joined
- Preparing for a security review or compliance check
- Understanding the current state of technical debt before a refactoring sprint
- Getting a performance baseline before an optimization effort
- Evaluating the architecture of a specific module or subsystem
Specify the scope explicitly: a single file, a directory, or the full project. A focused scope produces more actionable findings than a broad sweep.
How it works
- Define the scope — specify what to analyze: a file, a folder, or the whole project. Optionally indicate the focus area (security, performance, quality, or all).
- Deep read phase — the agent reads through all in-scope files systematically.
- Multi-dimensional analysis — findings are collected across code quality, security, architecture, performance, and tech debt.
- Report generated — a structured markdown report is produced with categorized findings, metrics, and recommendations.
- Report saved — the report is persisted to your Documents folder for future reference.
Key features
- Multi-dimensional — covers quality, security, architecture, performance, and technical debt in one pass
- Structured report — findings categorized by domain with severity and actionable recommendations
- Scope control — analyze a single file, a module, or the entire codebase
- Persistent output — the report is saved to Documents for ongoing reference
- Read-only — Analyze never modifies any files; it only observes and reports
Tips
State what you care about most. "Focus on security vulnerabilities in the authentication module" gets a more useful report than a generic full-project scan.
Use Analyze before a major refactoring sprint to establish a baseline. Re-run it after to measure the improvement.