fix-debt

Identify and resolve technical debt across specified code scopes.

Updated Jul 22, 2023
One-click install
npx skills add https://github.com/ValerianGuivarch/lsr-nestjs-backend --skill fix-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-debt
Source: https://github.com/ValerianGuivarch/lsr-nestjs-backend/tree/main/.claude/skills/fix-debt
Command: npx skills add https://github.com/ValerianGuivarch/lsr-nestjs-backend --skill fix-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the resolution of technical debt across one or more files in a codebase, providing a plan before any changes are made.

Core Features & Use Cases

  • Incremental Fixes: Targets and resolves tech debt incrementally, ensuring a controlled approach.
  • User-Defined Scope: Allows users to define the scope of tech debt resolution (domain, directory, file).
  • Debt Radar Integration: Can consume a debt-radar report or run an internal scan to identify violations.
  • Documentation and Validation: Always presents a fix plan for user validation before implementing changes.

Quick Start

Run the fix-debt skill on the 'libs/domain/api' directory to automatically resolve identified tech debt.

Frequently Asked Questions about fix-debt

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

FAQPage Schema
How do I automate technical debt resolution across my codebase?▼

Automate technical debt resolution by scanning specified directories or files to identify violations, then generating a detailed fix plan for user validation before applying incremental code refactoring changes.

Can I define the scope of tech debt fixes to target a specific domain or directory?▼

Yes, you can define the scope of tech debt fixes by specifying a domain, directory, or individual file, allowing targeted incremental code refactoring rather than applying changes across the entire codebase blindly.

Do I need a debt-radar report to identify technical debt violations before fixing them?▼

You do not need an existing debt-radar report to identify technical debt violations; the system can consume a report if available or run an internal scan to detect violations across your specified code scope.

What is the best way to plan code refactoring changes without breaking existing functionality?▼

The best way to plan code refactoring safely is to use an incremental approach that scans for technical debt, presents a detailed fix plan for validation, and applies changes only after user approval.

Are technical debt fixes applied automatically without user validation?▼

No, technical debt fixes are not applied automatically; the system always presents a detailed fix plan outlining the incremental changes required, ensuring user validation is obtained before any codebase modifications occur.