Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]
Scan codebases for technical debt, score severity, and generate prioritized remediation plans.
/tech-debt scan <project-dir> Scan for debt indicators
/tech-debt prioritize <inventory.json> Prioritize debt backlog
/tech-debt report <project-dir> Full dashboard with trends
/tech-debt scan ./src
/tech-debt scan . --format json
/tech-debt report . --format json --output debt-report.json
engineering/skills/tech-debt-tracker/scripts/debt_scanner.py — Scan for debt patterns (debt_scanner.py <directory> [--format json] [--output file])engineering/skills/tech-debt-tracker/scripts/debt_prioritizer.py — Prioritize debt backlog (debt_prioritizer.py <inventory.json> [--framework cost_of_delay|wsjf|rice] [--format json])engineering/skills/tech-debt-tracker/scripts/debt_dashboard.py — Generate debt dashboard (debt_dashboard.py [files...] [--input-dir dir] [--period weekly|monthly|quarterly] [--format json])→ engineering/skills/tech-debt-tracker/SKILL.md
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/tech-debt · pinned to the source commit
# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/tech-debt" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/alirezarezvani/claude-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 19392f7a08264ed00486a251f5b2098321771f94
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/.gemini/skills/tech-debt" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/tech-debt
Scanner static-checks@0.1.0 · commit 19392f7a0826. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.