tech-debt

Scan codebases for technical debt and create GitHub issues for high-severity findings.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/rioX432/live-translate --skill tech-debt-riox432
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/rioX432/live-translate/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/rioX432/live-translate --skill tech-debt-riox432

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify technical debt, code smells, architecture issues, test gaps, and dependency risks before they become costly maintenance problems.

Core Features & Use Cases

  • Codebase Scanning: Reviews repositories for duplicated code, long functions, large files, deep nesting, dead code, and TODO or FIXME markers.
  • Risk Triage: Groups findings by category and rates them by severity and effort so teams can prioritize the most impactful work.
  • Issue Creation: Opens GitHub issues for high-severity findings with enough context to support refactoring and follow-up.
  • Use Case: A maintainer can run this Skill on an active repository before a release to surface the highest-risk cleanup items and convert them into tracked work.

Quick Start

Ask the tech-debt skill to scan the repository and create GitHub issues for any high-severity findings.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I scan a codebase for technical debt and refactoring opportunities?

Scanning a codebase for technical debt involves detecting duplicated code, long functions, deep nesting, dead code, and TODO markers. The tool groups these refactoring opportunities by category, rating them by severity and effort so teams can prioritize maintenance work effectively.

Can I automatically create GitHub issues for code smells and architecture violations?

Yes, you can automatically create GitHub issues for high-severity code smells and architecture violations. The tool opens issues using the gh command, attaching file-level evidence and recommended fixes to support immediate refactoring and follow-up tracking.

What is the best way to triage technical debt before a software release?

The best way to triage technical debt before a release is to run an automated repository scan that surfaces test gaps, dependency issues, and performance hotspots. Findings are grouped by severity and estimated effort, allowing teams to address the highest-risk cleanup items first.

Does repository scanning detect test gaps and dependency issues?

Yes, repository scanning detects test gaps and dependency issues alongside dead code and performance hotspots. It evaluates the entire codebase to identify risks across categories, ensuring teams can address maintainability issues before they become costly maintenance problems.

How are technical debt findings prioritized for maintenance work?

Technical debt findings are prioritized by grouping them into categories and rating each item by severity and effort. This allows maintainers to quickly identify the most impactful refactoring targets and focus on high-severity items before a release or during active maintenance.