Features

Reports

Generate comprehensive code analysis reports

Stellarion can generate detailed reports about your codebase in multiple formats, helping you communicate code quality to stakeholders and track improvements over time.

Report Types

Overview Report

A high-level summary of your project:

  • Project metrics (files, lines of code, languages)
  • Overall health score
  • Test coverage summary
  • Language distribution
Generate an overview report for this project

Quality Report

Detailed code quality analysis:

  • Complexity metrics by file and function
  • Maintainability scores
  • Refactoring opportunities
  • Code smells detected
Generate a quality report showing complexity issues

Architecture Report

Dependency structure analysis:

  • Module relationships
  • Coupling metrics
  • Circular dependencies
  • Layer structure
Generate an architecture report showing dependencies

Technical Debt Report

Prioritized improvement opportunities:

  • Debt items with severity and effort
  • Priority rankings
  • ROI recommendations
  • Suggested action items
Generate a technical debt report for the src/ directory

Output Formats

FormatUse Case
JSONIntegration with other tools, automated processing
MarkdownDocumentation, GitHub/GitLab, readable reports
HTMLSharing with stakeholders, presentations
CSVSpreadsheet analysis, custom processing

Specifying Format

Generate a quality report in markdown format
Create a technical debt report as JSON

Saving Reports

Ask Claude Code to save reports to files:

Generate a quality report and save it to docs/quality-report.md

Filtering Reports

Focus on specific areas:

Generate a quality report for src/api/ only
Create a technical debt report excluding test files

Using Reports

Team Reviews

Share quality reports in code reviews to discuss improvements.

Sprint Planning

Use technical debt reports to prioritize refactoring work.

Stakeholder Updates

Generate overview reports to communicate codebase health.

Tracking Progress

Compare reports over time to measure improvement:

Generate a quality report. How does it compare to last month?

Best Practices

  • Generate reports regularly (weekly or per sprint)
  • Store reports in version control to track history
  • Focus on trends rather than absolute numbers
  • Use reports to start conversations, not as strict rules