skills.rest
vm0-ai
vm0-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tech-debt

Scan codebases for quality issues and generate GitHub tracking issues.

1.1k|68|Updated Nov 14, 2025
Search Tags:#refactoring#github#code-quality#static-analysis#turbo#issue-tracking#tech-debt
One-click install
npx skills add https://github.com/vm0-ai/vm0 --skill tech-debt-vm0-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/vm0-ai/vm0/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/vm0-ai/vm0 --skill tech-debt-vm0-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams proactively identify technical debt in the codebase and turn findings into trackable issues.

Core Features & Use Cases

  • Fast scan for code smells across the turbo/ directory and related code.
  • Generate GitHub issues from research results to drive remediation.
  • Use-case driven guidance for prioritization and planning of refactors.

Quick Start

Usage: research Usage: issue

  • Run the research operation to scan the codebase for debt. Then use issue to create a tracking item from the findings.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I identify technical debt in a codebase automatically?▼

You can identify technical debt automatically by running fast pattern scans for code smells across production and test code. This skill targets the turbo/ directory to generate structured findings and traceable tracking items for engineers.

How do I create GitHub issues from static analysis findings?▼

You can create GitHub issues from static analysis findings by running a research scan and then using the issue command. This converts the technical debt findings into traceable tracking items to drive codebase remediation.

What is the best way to track codebase refactoring tasks?▼

Tracking codebase refactoring tasks effectively requires generating traceable tracking items from quality issue scans. This skill enables engineers to create issues directly from research results to plan and prioritize refactors.

Does this technical debt scanner work with test code or only production code?▼

This technical debt scanner works with both test code and production code. It targets code health across the turbo/ directory and related directories, scanning for quality issues throughout the entire codebase.

How do I prioritize technical debt for refactoring?▼

To prioritize technical debt for refactoring, scan your codebase to generate structured findings and use the use-case driven guidance provided. This helps engineers plan remediation by turning quality issues into trackable items.

Related Skills

Explore More Software Engineering Skills→
davpatel605-beepdavpatel605-beep

github-auth

Configures GitHub authentication via tokens, SSH keys, or gh CLI for git and API workflows.

Community
Intermediate
anthony-chaudharyanthony-chaudhary
30

disambiguate-section

Map overloaded code tokens to distinct grounded concepts and generate GitHub issues.

Community
Advanced
Jaydpatel01Jaydpatel01

code-quality-and-review

Enforce code correctness, readability, and safety with linters and type checkers.

Community
Advanced
li3pli3p

debt-scan

Identify and prioritize technical debt in a codebase for remediation planning.

Community
Intermediate