ln-512-tech-debt-cleaner

Auto-fix low-risk code audit findings with confidence at least 90%.

Updated Mar 14, 2026

Search Tags:#automation #audit #static-analysis #code-cleanup #tech-debt #single-commit

Ready to run

npx skills add https://github.com/0xtaoist/taogate --skill ln-512-tech-debt-cleaner-0xtaoist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-512-tech-debt-cleaner
Source: https://github.com/0xtaoist/taogate/tree/main/ln-512-tech-debt-cleaner
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-512-tech-debt-cleaner-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cleaning up stale, low-risk tech debt is tedious and error-prone when done manually; this skill automates safe auto-fixes to improve code hygiene without touching business logic.

Core Features & Use Cases

Auto-fix safe findings: Remove unused imports, dead code, and adjust deprecated aliases with high confidence.
Single-commit hygiene: Group changes into one structured commit with a clear summary.
Audit-driven workflow: Integrates with codebase audit outputs (docs/project/codebase_audit.md) and supports standalone runs after ln-620 outputs.
Safety-first checks: Only apply fixes with confidence >=90% and verify via a safety checklist before committing.

Quick Start

Invoke the tech debt cleaner against the latest audit results to auto-fix eligible issues and generate a single commit summary.

Frequently Asked Questions about ln-512-tech-debt-cleaner

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

FAQPage Schema

How do I automate tech debt cleanup from static analysis findings?▼

Automating tech debt cleanup targets auto-fixable static analysis findings with high confidence. This skill verifies each fix against a safety checklist, applies changes bottom-up, runs lint and typecheck, and groups them into a single commit.

Does this code cleanup tool auto-fix findings with low confidence scores?▼

This code cleanup tool does not auto-fix low confidence findings. It strictly targets audit findings with a confidence score of 90% or higher to ensure safety and prevent unintended changes to business logic.

What is the best way to group multiple low-risk code fixes into a single commit?▼

The best way to group low-risk code fixes into a single commit is using an audit-driven workflow. This skill applies verified auto-fixes bottom-up and generates a single structured commit with a clear summary.

How do I remove dead code and unused imports automatically without breaking business logic?▼

To remove dead code and unused imports safely, this skill applies automated fixes only to high-confidence audit findings. It verifies changes against a safety checklist before committing to avoid touching business logic.

Do I need a codebase audit report before running automated tech debt cleanup?▼

Yes, you need a codebase audit report before running automated tech debt cleanup. The skill integrates with audit outputs like docs/project/codebase_audit.md to identify eligible auto-fixable issues for safe removal.

What are the limitations of automating tech debt cleanup with high confidence thresholds?▼

A limitation of automating tech debt cleanup with a 90% confidence threshold is that it skips numerous valid lower-confidence findings. It also focuses exclusively on safe auto-fixes and will not refactor complex business logic.