Stellarion helps you identify, categorize, and prioritize technical debt so you can make informed decisions about what to improve and when.
Functions or files that are too complex to maintain safely:
Code that's been copied instead of abstracted:
Structural issues that make the codebase harder to navigate:
Function signatures that are hard to use correctly:
Stellarion assigns priority based on:
| Factor | Weight | Description |
|---|---|---|
| Severity | High | How bad is the issue? |
| Frequency | Medium | How often is this code changed? |
| Impact | Medium | How critical is this code path? |
| Effort | Low | How hard is it to fix? |
Each issue includes an effort estimate:
| Level | Typical Time |
|---|---|
| Low | < 1 hour |
| Medium | 1-4 hours |
| Medium-High | 4-8 hours |
| High | 1-3 days |
Ask Claude Code to find technical debt:
Find all refactoring opportunities in this project.
Prioritize by severity and effort.
What's the most critical technical debt in src/api/?
Show me code duplication in this project.
Which duplicates should I consolidate first?
Don't try to fix everything at once. Pick high-priority, low-effort items first to build momentum.
Generate reports periodically to measure improvement:
Generate a technical debt report and save it.
Compare it to our previous report.
Establish team standards and catch new debt before it merges:
Check if any functions in this PR have complexity over 20.