skills.rest
BoraPerusic
BoraPerusicCOMMUNITY
Explore all skills by this author →
GitHub

code-refactoring-tech-debt

Identify and quantify technical debt across code, architecture, testing, documentation, and infrastructure.

Updated Apr 12, 2026
Search Tags:#architecture#refactoring#code-quality#velocity#roi#technical-debt
One-click install
npx skills add https://github.com/BoraPerusic/agents --skill code-refactoring-tech-debt-boraperusic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-refactoring-tech-debt
Source: https://github.com/BoraPerusic/agents/tree/main/skills/to%20try/code-refactoring-tech-debt
Command: npx skills add https://github.com/BoraPerusic/agents --skill code-refactoring-tech-debt-boraperusic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies, quantifies, and prioritizes technical debt across software projects to speed delivery and reduce maintenance costs.

Core Features & Use Cases

  • Technical Debt Inventory across code, architecture, testing, documentation, and infrastructure
  • Impact assessment with ROI and risk scoring
  • Roadmaps with quick wins, medium-term refactors, and long-term architecture redesign
  • Prevention gates and governance

Quick Start

Run a comprehensive debt inventory across the repository to surface hotspots and establish remediation priorities.

Frequently Asked Questions about code-refactoring-tech-debt

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

FAQPage Schema
What is the best way to quantify technical debt across a codebase?▼

To quantify technical debt, run a comprehensive inventory across your codebase to surface hotspots and establish remediation priorities. This identifies and measures debt across code, architecture, testing, documentation, and infrastructure to prioritize remediation efforts.

How do I calculate the ROI of refactoring technical debt?▼

Calculate the ROI of refactoring technical debt by performing an impact assessment that scores risk against expected delivery velocity improvements. This process prioritizes remediation efforts based on measurable impact and risk scoring across your software projects.

Can I use this to plan architecture redesigns for technical debt?▼

Yes, you can plan architecture redesigns for technical debt using phased remediation roadmaps. The approach supports scenarios from small fixes to large-scale architecture redesigns, organizing work into quick wins, medium-term refactors, and long-term plans.

How do I create a technical debt inventory for documentation and infrastructure?▼

You create a technical debt inventory for documentation and infrastructure by scanning the repository to identify debt across all project layers. This comprehensive inventory process surfaces hotspots beyond just code, covering architecture and testing debt as well.

When do I need prevention gates for technical debt governance?▼

You need prevention gates for technical debt governance after establishing your remediation roadmaps and quick wins. These governance mechanisms help maintain code quality and prevent the accumulation of new debt across your software projects.

Related Skills

Explore More Software Engineering Skills→
artk0deartk0de
11

brainstorming

Enrich creative code brainstorming with git-based technical debt and hotspot signals.

Community
Advanced
TravisLeeeeeeTravisLeeeeee
110

Workflow Optimizer

Map current-state workflows, identify bottlenecks, and design optimized future-state improvements.

Community
Advanced
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
AisleiAvilaAisleiAvila

dependency-management-deps-audit

Audit project dependencies for vulnerabilities, licensing issues, and supply-chain risks.

Community
Advanced