tech-debt-tracker

Scans codebases to identify, categorize, and prioritize technical debt.

Updated Aug 1, 2025

Search Tags:#code quality #code analysis #refactoring #technical debt #developer productivity #debt management

Ready to run

npx skills add https://github.com/wichan7/devlog --skill tech-debt-tracker-wichan7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt-tracker
Source: https://github.com/wichan7/devlog/tree/main/.claude/skills/tech-debt-tracker
Command: npx skills add https://github.com/wichan7/devlog --skill tech-debt-tracker-wichan7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires json, os, re, ast, collections, datetime, pathlib, typing, dataclasses, statistics, math, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps engineering teams systematically identify, prioritize, and manage technical debt, leading to cleaner code, faster development, and reduced bugs.

Core Features & Use Cases

Automated Code Scanning: Detects various types of technical debt like complexity, duplication, and security vulnerabilities.
Prioritized Remediation Plans: Ranks debt items based on business impact and effort, creating actionable backlogs.
Trend Analysis: Tracks debt over time to measure progress and identify recurring issues.
Use Case: A team struggling with slow feature development can use this Skill to scan their codebase, identify the top 5 debt items hindering progress, and create a prioritized plan to address them in the next sprint.

Quick Start

Use the tech-debt-tracker skill to scan the current project directory for technical debt.

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?▼

You can identify technical debt by scanning your codebase to detect complexity, duplication, and vulnerabilities, then calculate its impact on development velocity to generate prioritized remediation plans using frameworks like Cost of Delay and WSJF.

What is technical debt impact on developer velocity and code quality?▼

Technical debt impacts developer velocity and code quality by slowing feature development and increasing bugs; it is measured by calculating the impact of complexity and duplication on your codebase and tracking debt trends over time.

Can I track technical debt remediation progress and trend analysis over time?▼

Yes, you can track technical debt remediation progress through trend analysis, which monitors debt metrics over time to measure improvements and identify recurring codebase issues.

Does technical debt scanning require Python scripts to run in the project directory?▼

Yes, technical debt scanning requires Python scripts for scanning, prioritizing, and dashboarding debt metrics within your current project directory.

What's the best way to create a prioritized refactoring backlog for a sprint?▼

The best way to create a prioritized refactoring backlog is to scan your codebase for technical debt, rank items based on business impact and effort using WSJF, and generate an actionable remediation plan for your next sprint.