cleanup-dead-code

Detect and auto-remediate dead code and unused exports in JavaScript/TypeScript projects.

18|11|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Intense-Visions/harness-engineering --skill cleanup-dead-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup-dead-code
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/cleanup-dead-code
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill cleanup-dead-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find and remove dead code, unused exports, and entropy-induced pattern violations without breaking builds.

Core Features & Use Cases

  • Entropy reporting and health metrics for large codebases
  • Safe auto-fixes for dead exports, unused files, and orphaned dependencies
  • Convergence-driven cleanup with validation to preserve behavior

Quick Start

Run the cleanup skill to analyze entropy, identify dead code, and apply safe fixes.

Frequently Asked Questions about cleanup-dead-code

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

FAQPage Schema
How do I automatically find and remove dead code in a JavaScript monorepo?

You can automate dead code detection in a JavaScript monorepo by scanning for dead exports, unused files, and orphaned dependencies, then applying convergence-driven auto-fixes with validation to ensure safe removal.

What is entropy reporting and how does it keep a TypeScript codebase healthy?

Entropy reporting measures codebase health by identifying dead code and pattern violations in TypeScript projects, allowing you to safely auto-fix issues and prevent entropy-induced decay without breaking builds.

Can I safely auto-fix unused exports without breaking my existing builds?

Yes, you can safely auto-fix unused exports by running a convergence-driven cleanup loop that validates behavior and runs tests before applying changes, ensuring dead code removal does not break builds.

How do I identify and clean up orphaned dependencies in my codebase?

To clean up orphaned dependencies, you can scan your codebase to detect unused packages and apply safe auto-remediation, using validation and tests to confirm behavior remains intact after removal.

Does this dead code cleanup approach work with both TypeScript and JavaScript projects?

Yes, this dead code cleanup approach works with both TypeScript and JavaScript projects, including monorepos, by scanning for dead exports, unused files, and pattern violations to maintain code health.