tech-debt-review

Coordinate ten analysis agents to produce a consolidated technical debt report.

4|11|Updated Dec 14, 2025

Search Tags:#audit #analysis #reporting #code-quality #technical-debt #trend

Ready to run

npx skills add https://github.com/Obsidian-Owl/floe --skill tech-debt-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-debt-review
Source: https://github.com/Obsidian-Owl/floe/tree/main/.claude/skills/tech-debt-review
Command: npx skills add https://github.com/Obsidian-Owl/floe --skill tech-debt-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing and understanding technical debt across large codebases is time-consuming and error-prone; this skill orchestrates multiple specialized analyses to produce a single, actionable debt report.

Core Features & Use Cases

End-to-end debt analysis across codebases for PR readiness, periodic health checks, and maintainability investigations.
Cross-category findings including code complexity, dead code, dependencies, documentation, testing, TODOs, hotspots, performance, and architecture.
Trend tracking and historical auditing with saved reports for cross-version comparisons.

Quick Start

Run a full technical debt audit on your repository to generate a prioritized report and actionable remediation plan.

Frequently Asked Questions about tech-debt-review

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

FAQPage Schema

How do I quantify technical debt across a large codebase?▼

Technical debt is quantified by coordinating ten specialized analysis agents to evaluate code complexity, dead code, dependencies, documentation, testing, and architecture, producing a consolidated debt report with prioritized remediation recommendations.

What is the best way to track technical debt trends over time?▼

Technical debt trends are tracked by persisting full audits for historical comparison. This allows cross-version trend analysis to monitor maintainability improvements or degradation across periodic repository health checks.

How do I audit code complexity and dead code for a maintainability investigation?▼

Code complexity and dead code are audited alongside dependencies, documentation, testing, TODOs, hotspots, performance, and architecture by running a full repository analysis to identify maintainability issues and quantify debt.

What categories of technical debt are included in a consolidated code analysis report?▼

A consolidated code analysis report includes cross-category findings covering code complexity, dead code, dependencies, documentation, testing, TODOs, hotspots, performance, and architecture across the full repository or targeted paths.

Can I generate a prioritized remediation plan for technical debt findings?▼

A prioritized remediation plan is generated as part of the executive summary, providing actionable recommendations based on the consolidated debt findings from the multi-agent codebase analysis.