stellarion_tech_debt_report [Pro]
Produces an aggregated technical debt report by combining multiple quality signals: complexity hotspots (cyclomatic > 15, cognitive > 20), public functions without tests, high-coupling modules (> 15 dependencies), unused exports, and oversized files (> 30 functions or > 1000 lines). Each item is scored by severity and estimated effort.
When to Use
- To prioritize refactoring work during a cleanup sprint
- To build a case for paying down technical debt with stakeholders
- To identify the highest-impact improvements with the least effort
- Before planning a large feature to understand which areas of the codebase need attention first
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
category | enum | No | all | Filter by debt category: complexity, cognitive_complexity, missing_tests, high_coupling, unused_code, large_file |
severity | enum | No | low | Minimum severity to include: low, medium, high, critical |
limit | number | No | 50 | Maximum number of items to return |
Examples
Full debt report
Show me all the technical debt in this project.
Returns a comprehensive list of all debt items across all categories, sorted by severity.
Focus on complexity issues
What are the most complex functions? Show me anything with high cyclomatic or cognitive complexity.
Uses category: "complexity" (or "cognitive_complexity") to filter to complexity-related debt.
Find untested public APIs
Which public functions don't have tests?
Uses category: "missing_tests" to list public functions with no corresponding test function.
Critical issues only
Show me only the critical technical debt — the stuff that needs fixing now.
Sets severity: "critical" to filter to the highest-priority items.
Top 10 worst offenders
Give me the top 10 worst technical debt items.
Sets limit: 10 to return only the highest-scoring items.
Output Format
Each debt item includes:
- File path and line number — location of the issue
- Category — which type of debt:
complexity,cognitive_complexity,missing_tests,high_coupling,unused_code, orlarge_file - Symbol name — the function, class, or module involved
- Severity —
low,medium,high, orcritical - Score — numeric value backing the severity (e.g., cyclomatic complexity of 28)
- Effort estimate — rough effort to fix:
trivial,small,medium,large - Description — human-readable explanation
Severity thresholds
| Category | Medium | High | Critical |
|---|---|---|---|
| Cyclomatic complexity | > 15 | > 25 | > 40 |
| Cognitive complexity | > 20 | > 30 | > 50 |
| Missing tests | public function | public API entry point | exported from package |
| High coupling | > 15 deps | > 25 deps | > 40 deps |
| Large file | > 30 functions | > 50 functions | > 80 functions |
Tips
- Sort by severity and effort to find "quick wins" — high-severity items with trivial or small effort
- The
missing_testscategory only flags public functions — internal helpers are excluded to reduce noise high_couplingmeasures efferent coupling (outgoing dependencies) — a module with 20+ dependencies is fragile- Use
categoryfilters to generate focused reports for specific team discussions - Combine with
stellarion_codebase_healthfor the big picture, then drill into debt details here - Re-run after paying down debt to track progress