skills.rest
coolbeevip
coolbeevipCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

team-tech-debt-analyze

Analyze technical debt via read-only inspection and evidence-based reports.

8|1|Updated May 10, 2026
Search Tags:#code health check#maintainability audit#technical debt analysis#over-engineering detection#dependency simplification
One-click install
npx skills add https://github.com/coolbeevip/team-ai-skills --skill team-tech-debt-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-tech-debt-analyze
Source: https://github.com/coolbeevip/team-ai-skills/tree/main/skills/tech-debt/team-tech-debt-analyze
Command: npx skills add https://github.com/coolbeevip/team-ai-skills --skill team-tech-debt-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive analysis of technical debt within a project or module, offering evidence-based maintainability and stability reports to guide the debt management process.

Core Features & Use Cases

  • Technical Debt Analysis: Conducts a read-only inspection to identify technical debt candidates with source code evidence.
  • Evidence-Driven Reporting: Outputs detailed reports on maintainability, stability, testing, architecture, and delivery risks.
  • Integration with Debt Management Process: Integrates with subsequent steps in the technical debt management workflow, such as refinement and issue creation.

Quick Start

Run the team-tech-debt-analyze skill to initiate a technical debt analysis on your project.

Frequently Asked Questions about team-tech-debt-analyze

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

FAQPage Schema
How do I perform a technical debt analysis on my codebase?▼

A maintainability audit evaluates code health by collecting source code evidence through read-only inspection. It identifies technical debt candidates and outputs detailed reports covering architecture, stability, and delivery risk assessment.

Can I detect over-engineering and dependency issues during a code health check?▼

Yes, a code health check identifies over-engineering and dependency simplification opportunities. It uses read-only inspection to gather source code evidence, producing stability and architecture reports that highlight specific technical debt candidates.

Does the technical debt analysis modify my source code during inspection?▼

No, the technical debt analysis uses read-only inspection to identify debt candidates and collect source code evidence. It safely evaluates maintainability, stability, and architecture without modifying your project files.

What's the best way to report delivery risks and stability issues found in a project?▼

The best way to report delivery risks and stability issues is to generate evidence-driven reports from a technical debt analysis. These detailed reports use collected source code evidence to guide subsequent debt management and refinement workflows.

How do I integrate technical debt findings with issue tracking tools?▼

You integrate technical debt findings with issue tracking tools by using the evidence-based reports generated from the analysis. These reports identify specific debt candidates and delivery risks, serving as direct inputs for subsequent issue creation and refinement steps.

Related Skills

Explore More Software Engineering Skills→
bahayonghangbahayonghang
16

code-quality-review

Review source code for maintainability, abstraction quality, and branching complexity.

Community
Advanced
devmuslimdevmuslim

tech-debt-log

Log and prioritize technical debt items with impact and effort details.

Community
Basic
ttmousettmouse
35

task-decomposer

Decompose high-level tasks into actionable subtasks with dependency tracking.

Community
Advanced
chijunzhengchijunzheng

code-review

Review code across languages for defects, standards, and technical debt.

Community
Advanced