skills.rest
nikhillinit
nikhillinitCOMMUNITY
Explore all skills by this author →
GitHub

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Updated Jul 21, 2025
Search Tags:#refactoring#metrics#technical debt#prioritization#code-quality
One-click install
npx skills add https://github.com/nikhillinit/Updog_restore --skill tech-debt-tracker-nikhillinit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt-tracker
Source: https://github.com/nikhillinit/Updog_restore/tree/main/.claude/skills/workflow-engine/tech-debt-tracker
Command: npx skills add https://github.com/nikhillinit/Updog_restore --skill tech-debt-tracker-nikhillinit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides automated identification, measurement, and prioritization of technical debt across a codebase.

Core Features & Use Cases

  • Debt identification: Detects complexity, duplication, churn, and missing tests.
  • Metrics calculation: Compute SQALE, maintainability, and churn indices.
  • Prioritization & backlog generation: Rank debt items by impact and effort to guide refactors.

Quick Start

Run a quick scan or generate a prioritized backlog for the next sprint.

Frequently Asked Questions about tech-debt-tracker

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

FAQPage Schema
How do I identify and prioritize technical debt in my codebase?▼

Technical debt prioritization automatically detects complexity, duplication, churn, and missing tests across your codebase, then ranks items by impact and effort to guide refactoring decisions. Run a scan to generate a prioritized backlog actionable for your next sprint.

What metrics does technical debt tracking measure?▼

Debt tracking computes SQALE, maintainability, and churn indices alongside code-quality signals like complexity and duplication. These metrics quantify debt severity and provide stakeholder-ready reports for planning refactoring work.

Can I use technical debt tracking across multiple programming languages?▼

Yes, debt identification and metrics calculation work across languages and project scales. Configure thresholds for your codebase to detect complexity, duplication, and coverage gaps regardless of language.

How do I generate a backlog from technical debt scans?▼

Structured debt items are generated from scan results ranked by impact and effort. Export actionable backlog items with configurable thresholds to prioritize refactoring across your team's upcoming sprints.

What indicators does the tool use to detect technical debt?▼

Debt detection scans for complexity, code duplication, file churn, missing test coverage, and code smells. Configurable thresholds let you define what constitutes debt in your specific codebase context.

Related Skills

Explore More Software Engineering Skills→
CENKSSSCENKSSS

coverage-drop-investigator

Detect test coverage regressions and trace them to specific commits and files.

Community
Intermediate
cy-walicy-wali

sprint-planning

Generate a sprint plan document with goals, capacity, backlog, risks, and DoD.

Community
Intermediate
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
CarGDevCarGDev

Code Auditor

Audit code quality by detecting dead code, complexity, duplication, and architectural smells.

Community
Intermediate