tech-debt

Scan codebases for technical debt and generate prioritized severity reports.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/aigars-stg/stg-mvp --skill tech-debt-aigars-stg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/aigars-stg/stg-mvp/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/aigars-stg/stg-mvp --skill tech-debt-aigars-stg

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the identification and prioritization of technical debt within a codebase, providing a clear roadmap for improvement.

Core Features & Use Cases

  • Comprehensive Scanning: Analyzes code for issues across 12 predefined categories, including test coverage, security vulnerabilities, type safety, and more.
  • Prioritized Reporting: Generates a structured report that highlights the most critical issues first, enabling focused remediation efforts.
  • Use Case: A development team can use this Skill to regularly assess the health of their project, ensuring that technical debt does not accumulate and hinder future development velocity.

Quick Start

Run a full technical debt scan across the codebase.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I scan my codebase to identify and prioritize technical debt?

A technical debt scan identifies code quality issues, security vulnerabilities, and test coverage gaps, then prioritizes them by severity. This process uses grep and glob to analyze the codebase across 12 categories, generating an actionable remediation report.

What is technical debt and how is it measured during a code analysis?

Technical debt represents the implied cost of future rework caused by choosing an easy solution now. This Skill measures it by scanning code for security vulnerabilities, type safety issues, and test coverage gaps across 12 categories, prioritizing findings by severity.

Can I run a focused technical debt scan for just security vulnerabilities or type safety?

Yes, you can run focused category deep-dives to target specific issues like security vulnerabilities or type safety. The Skill supports both full codebase scans and targeted analysis to help you assess and remediate specific areas of technical debt.

Does this technical debt analysis tool require Supabase MCP to run?

Yes, the scan utilizes Supabase MCP tools alongside standard grep and glob utilities to execute structured code analysis. These components enable the identification and prioritization of codebase issues across 12 categories.

What's the best way to automate code quality and refactoring prioritization for my project?

The best way to automate refactoring prioritization is running a structured technical debt scan regularly. It analyzes the codebase for code quality issues and generates a prioritized report with severity levels to ensure debt does not hinder development velocity.