sonar_analyze_patterns

Intelligently analyze and group SonarQube issues to identify patterns, correlations, and provide actionable insights.

Description

Groups issues by selected strategy to help prioritize fixing. Provides fixability scoring, time estimates, and impact analysis for efficient batch fixing.

Parameters

Parameter	Type	Required	Default	Description
groupBy	string	No	pattern	Grouping: pattern, file, severity, fixability
includeImpact	boolean	No	false	Include time/effort estimates
includeCorrelations	boolean	No	false	Identify related issues

Grouping Strategies

Strategy	Groups By	Best For
pattern	Rule/issue type	Finding repeated problems
file	File location	File-focused cleanup
severity	Issue severity	Priority-based fixing
fixability	Fix difficulty	Automation planning

Usage

Group by Pattern

Show me common issue patterns in this project

Tool call:

{
  "groupBy": "pattern"
}

Group by Fixability

Which issues can I auto-fix?

Tool call:

{
  "groupBy": "fixability",
  "includeImpact": true
}

Full Analysis

Give me a complete analysis with correlations

Tool call:

{
  "groupBy": "pattern",
  "includeImpact": true,
  "includeCorrelations": true
}

Response Format

By Pattern

ISSUE PATTERN ANALYSIS
━━━━━━━━━━━━━━━━━━━━━━

Total Issues: 47
Unique Patterns: 12

TOP PATTERNS:

1. typescript:S1854 - Remove unused variables (15 issues)
   Fixability: AUTO
   Files affected: 8
   Effort: 15min total

2. typescript:S3776 - Reduce cognitive complexity (8 issues)
   Fixability: MODERATE
   Files affected: 5
   Effort: 2h total

3. typescript:S3649 - SQL Injection (2 issues)
   Fixability: MANUAL
   Files affected: 2
   Effort: 1h total
   Priority: HIGH - Security vulnerability

By Fixability

FIXABILITY ANALYSIS
━━━━━━━━━━━━━━━━━━━

AUTO-FIXABLE (23 issues):
  - Remove unused imports (12)
  - Use const instead of let (8)
  - Remove unused variables (3)
  Total effort: 30min

MODERATE (16 issues):
  - Reduce complexity (8)
  - Add return types (5)
  - Extract functions (3)
  Total effort: 4h

MANUAL (8 issues):
  - SQL injection fixes (2)
  - Refactor god class (3)
  - Fix race conditions (3)
  Total effort: 8h

RECOMMENDATION:
Start with AUTO-FIXABLE issues for quick wins.
Impact: Resolves 49% of issues in 30 minutes.

By File

FILE-BASED ANALYSIS
━━━━━━━━━━━━━━━━━━━

FILES WITH MOST ISSUES:

1. src/services/UserService.ts (12 issues)
   - 5 code smells
   - 4 bugs
   - 3 vulnerabilities
   Effort: 3h

2. src/api/handlers.ts (8 issues)
   - 6 code smells
   - 2 bugs
   Effort: 2h

3. src/utils/helpers.ts (6 issues)
   - 6 code smells
   Effort: 1h

Examples

Example 1: Plan a Cleanup Sprint

Prompt:

Help me plan which issues to tackle first this sprint

Tool Call:

{
  "groupBy": "fixability",
  "includeImpact": true
}

Example 2: Find Quick Wins

Prompt:

What can I fix quickly with minimal effort?

Tool Call:

{
  "groupBy": "fixability"
}

Example 3: Security Focus

Prompt:

Group all security-related issues

Tool Call:

{
  "groupBy": "severity",
  "includeCorrelations": true
}

Fixability Levels

Level	Description	Typical Issues
AUTO	Can be fixed automatically	Unused imports, formatting
EASY	Simple manual fix	Add null check, type annotation
MODERATE	Requires some thought	Reduce complexity, refactor
MANUAL	Significant work needed	Architecture changes, security

Best Practices

1. Start with AUTO - Get quick wins first
2. Batch by pattern - Fix all instances of same issue
3. Check correlations - Related issues often have shared fixes
4. Use impact data - Focus on high-impact changes

Related Tools

• sonar_get_issue_details - Deep dive on specific issues
• sonar_get_technical_debt - Debt prioritization
• sonar_scan_project - Verify fixes