tech-debt

Scan codebases to identify technical debt and update a prioritized debt register.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill tech-debt-brand6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill tech-debt-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

跨代码库追踪、分类并优先排序技术债务,帮助开发团队可视化负债、避免积压及风险累积。

Core Features & Use Cases

  • Debt discovery: 自动识别代码中的待办、待知标记和已废弃等债务指标,并提取出潜在问题。
  • Classification & Prioritization: 将债务按架构、代码质量、测试、文档、依赖、性能等类别归类并给出优先级排序。
  • Debt register: 维护一个中央登记表并为还债工作提供冲刺就绪的排期建议。
  • Use Case: 在拥有多仓库的项目中,持续暴露债务项,帮助各团队协同规划修复工作。

Quick Start

Run a scan across your codebase to identify debt indicators and update the debt register for prioritization.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I track technical debt across multiple repositories?

To track technical debt across multiple repositories, scan codebases to identify debt indicators and maintain a central debt register for cross-repo visualization and risk management.

What is the best way to prioritize code quality issues for a sprint?

The best way to prioritize code quality issues is to classify debt by category and generate sprint-ready prioritization suggestions from a central debt register.

How does a debt register work for managing technical debt?

A debt register works by logging classified technical debt items identified during codebase scans, providing a centralized ledger for prioritization and sprint planning.

Can I integrate codebase scanning for tech debt into my CI workflow?

Yes, you can integrate repository scanning into CI workflows to continuously surface technical debt indicators and automatically update the debt register.

What categories of technical debt can be identified during a repo scan?

A repo scan identifies technical debt by classifying indicators into categories including architecture, code quality, testing, documentation, dependencies, and performance.

When do I need a formal debt ledger for my codebase?

You need a formal debt ledger when managing multi-repo projects to avoid backlog accumulation, track debt indicators, and coordinate prioritized repayment across teams.