tech-debt

Scan codebases for unused code and temporary files, then remove them with approval.

15|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/bluredengine/blured --skill tech-debt-bluredengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/bluredengine/blured/tree/main/.claude/skills/tech-debt
Command: npx skills add https://github.com/bluredengine/blured --skill tech-debt-bluredengine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you manage and reduce technical debt in your codebase by identifying and removing unused code, temporary files, and other cruft.

Core Features & Use Cases

  • Tech Debt Analysis: Identifies obsolete files, temporary files, unused code, dead imports, and other unnecessary elements.
  • Cleanup Automation: Automates the process of removing identified tech debt items based on user approval.
  • Use Case: If you're looking to clean up your codebase, remove unused code, or reduce tech debt, this Skill can help streamline the process.

Quick Start

Run the tech-debt skill to scan your codebase and automatically remove identified tech debt items.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I find and remove unused code in my codebase?

To find and remove unused code in your codebase, you can run an automated scan to identify dead imports, obsolete files, and temporary files. The identified technical debt is then automatically removed based on your approval.

What is technical debt and how does automated cleanup work?

Technical debt includes obsolete files, temporary files, and dead imports that accumulate in a codebase. Automated cleanup works by scanning your project to identify these unnecessary elements and removing them after you approve the changes.

What's the best way to automate codebase maintenance and remove temporary files?

The best way to automate codebase maintenance is to use a scanning tool that identifies temporary files and dead code. This streamlines the cleanup process by flagging unnecessary elements for removal and executing the deletion upon your approval.

Can I scan for obsolete files and dead imports without manually reviewing the entire codebase?

Yes, you can scan for obsolete files and dead imports without manual review by running an automated technical debt analysis. This process detects unused code and temporary files across your codebase, presenting them for your approval before removal.

Do I need to approve codebase cleanup actions before unused code is deleted?

Yes, you need to approve codebase cleanup actions before unused code is deleted. The scanning process identifies technical debt items, but the automated removal only executes once you grant explicit approval for the changes.

Why should I use an automated tool for technical debt removal instead of manual codebase cleanup?

You should use an automated tool for technical debt removal because manual codebase cleanup is time-consuming and prone to missing dead imports or temporary files. Automated scanning comprehensively identifies cruft and streamlines the removal process efficiently.