analyze-quality

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Goal

Perform comprehensive codebase quality analysis to identify improvement opportunities and generate prioritized recommendations.

Key Capabilities:

1. Test Coverage Gaps: Find files without tests
2. Architecture Issues: Detect anti-patterns and violations
3. Missing Documentation: Identify undocumented code
4. Performance Issues: Find optimization opportunities
5. Security Issues: Detect vulnerabilities
6. Quality Scoring: Calculate module-level quality scores
7. LSP Analysis (v3.8.0+): Language-aware analysis using LSP tools

Coverage: Provides holistic codebase health assessment

LSP Integration (Claude Code 2.1.0+): When --lsp flag is provided or TypeScript project is detected:

• Semantic analysis of unused imports/exports
• Dead code detection via reference analysis
• Type error detection
• Symbol resolution for accurate metrics

---

Execution Steps

1. Initialize Analysis Context

YOU MUST NOW initialize the analysis using the Bash tool:

1. Get repository root:

   git rev-parse --show-toplevel 2>/dev/null || pwd
   

   Store as REPO_ROOT.

2. Display analysis banner:

   📊 Codebase Quality Analysis
   ============================
   
   Analyzing: {REPO_ROOT}
   Started: {TIMESTAMP}
   

3. Detect project type by reading package.json:

   • Framework: Vite, Next.js, Remix, CRA, or Generic
   • Language: JavaScript, TypeScript, Python, Go, etc.
   • Test framework: Vitest, Jest, Pytest, etc.

---

1.5. LSP-Based Analysis (Enhanced)

IF --lsp flag is provided OR TypeScript project detected, use LSP for semantic analysis: