skills.rest
jdforsythe
jdforsytheCOMMUNITY
Explore all skills by this author →
GitHub

wolfe-tech-debt

Identify and report technical debt with interest calculated from code churn and complexity.

Updated Jun 15, 2026
Search Tags:#quality assurance#code analysis#refactoring#technical debt#automated code review
One-click install
npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-tech-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wolfe-tech-debt
Source: https://github.com/jdforsythe/wolfe-pack/tree/main/templates/bots/wolfe-tech-debt
Command: npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-tech-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies and reports technical debt within a codebase, streamlining the process of addressing such issues.

Core Features & Use Cases

  • Technical Debt Identification: Scans code for issues such as duplication, shallow modules, dead code, and more.
  • Interest Calculation: Ranks findings by the interest they accrue based on code churn and complexity.
  • Behavior Preservation: Ensures that refactors do not change the behavior of the code.
  • Verification and Reporting: Verifies findings and reports them with detailed information for human review.

Quick Start

Run the 'wolfe-tech-debt' command with the specific area you want to scan, e.g., 'wolfe-tech-debt backend'.

Frequently Asked Questions about wolfe-tech-debt

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

FAQPage Schema
How do I identify technical debt in my codebase automatically?▼

Technical debt identification scans your codebase to detect issues like duplication, shallow modules, and dead code. This skill calculates interest based on code churn and complexity, verifying findings before reporting them for human review.

How is technical debt interest calculated from code churn and complexity?▼

Interest calculation ranks technical debt findings by analyzing code churn and complexity metrics. This highlights areas where refactoring provides the highest value, helping prioritize development efforts effectively.

Do I need a specific index to scan for technical debt?▼

Yes, scanning for technical debt requires access to the codebase and the wolfe-pack index. You must have these prerequisites configured before running the analysis on your target area.

How do I scan a specific area of my project for code issues?▼

To scan a specific area for code issues, run the command targeting that directory, such as specifying 'backend'. The tool will analyze that scope and report findings with detailed information for review.

Does refactoring technical debt change the behavior of my code?▼

No, behavior preservation ensures that refactors do not change the code's behavior. The technical debt analysis verifies all findings to guarantee functionality remains intact before reporting.

What is the best way to prioritize refactoring tasks in a large codebase?▼

The best way to prioritize refactoring is by calculating technical debt interest. By ranking findings based on code churn and complexity, you can address the most costly issues first.

Related Skills

Explore More Software Engineering Skills→
jdforsythejdforsythe

wolfe-bugs

Scan codebases to identify and verify bugs with reproducer tests.

Community
Advanced
MohammedSaudAlsahliMohammedSaudAlsahli

improve-codebase-architecture

Analyze codebases for architectural friction and generate visual HTML reports.

Community
Advanced
viktorbezdekviktorbezdek
10

moai-workflow-testing

Automate end-to-end development workflows integrating testing, debugging, profiling, and code review.

Community
Advanced
mikkeymoomikkeymoo
1

mm-cleanup

Automate dead code, duplication, and AI padding removal in Python and JavaScript files.

Community
Advanced