tech-debt-tracker

Scan codebases for technical debt, prioritize remediation, and track debt trends over time.

Updated May 21, 2025
One-click install
npx skills add https://github.com/nielslataire/Group-LN --skill tech-debt-tracker-nielslataire
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-tracker
Source: https://github.com/nielslataire/Group-LN/tree/main/.claude/skills/tech-debt-tracker
Command: npx skills add https://github.com/nielslataire/Group-LN --skill tech-debt-tracker-nielslataire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Engineering teams accumulate technical debt that silently slows development velocity and increases maintenance costs, but they lack a systematic way to detect, quantify, and prioritize it. This Skill turns vague concerns about code quality into a scored, prioritized backlog with trend analysis and executive-ready reporting. ## Core Features & Use Cases - Automated Debt Detection: Scan Python, JavaScript, Java, C#, Go, and other codebases to detect 15+ debt types including large functions, high complexity, duplicate code, security risks, and missing documentation. - Intelligent Prioritization: Score debt items using Cost of Delay, WSJF, or RICE frameworks with effort estimation, interest rate calculation, and sprint allocation recommendations. - Trend Analysis & Dashboards: Compare historical scans to compute health scores (0-100), debt velocity, forecasts, and strategic recommendations for stakeholders. - Use Case: Run the scanner on your repository before sprint planning, feed the inventory into the prioritizer to select high-impact quick wins, then generate a quarterly dashboard showing health score improvement to leadership. ## Quick Start Ask the assistant to scan your project directory for technical debt and produce a prioritized remediation backlog with a health score summary.

Frequently Asked Questions about tech-debt-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a codebase for technical debt automatically?▼

Run the debt scanner script against your project directory to detect issues like large functions, high complexity, duplicates, and security risks. It outputs JSON for tooling or human-readable text reports, with configurable thresholds via a config file.

What prioritization frameworks can I use for tech debt backlogs?▼

The prioritizer supports Cost of Delay, Weighted Shortest Job First (WSJF), and RICE frameworks. Each scores items by business impact, urgency, risk reduction, and effort, then generates sprint allocation recommendations based on your team size and capacity.

Which programming languages does the debt scanner support?▼

The scanner uses AST parsing for Python and regex-based pattern detection for JavaScript, TypeScript, Java, C#, Go, and other languages. File extension mappings and ignore patterns are configurable through a JSON config file.

How do I track technical debt trends over time?▼

Save scanner output from multiple points in time, then run the dashboard tool on those files or a directory of scans. It computes health score trends, debt velocity, forecasts, and an executive summary with strategic recommendations.

Why does the debt dashboard show flat or unreliable trends?▼

Trend analysis requires at least two historical snapshots, and meaningful forecasts need several data points spaced over time. Ensure scan files contain consistent formats and that filenames or metadata include usable dates.

Can I integrate tech debt scanning into a CI/CD pipeline?▼

Yes, run the scanner in your CI script to produce a JSON report on each build, then compare results against a baseline to fail builds when critical issues appear. The JSON output format is designed for automated tooling consumption.