dead-code

Analyze codebases to identify unreachable declarations, dead control flow, and phantom dependencies.

12|Updated Mar 3, 2026

Search Tags:#code quality #refactoring #technical debt #code audit #dead code #unused code

Ready to run

npx skills add https://github.com/KilimcininKorOglu/cli-tweaks --skill dead-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dead-code
Source: https://github.com/KilimcininKorOglu/cli-tweaks/tree/main/claude/skills/dead-code
Command: npx skills add https://github.com/KilimcininKorOglu/cli-tweaks --skill dead-code

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill tackles the issue of code bloat and technical debt by systematically identifying and reporting on dead code, unused declarations, and phantom dependencies within a codebase.

Core Features & Use Cases

Comprehensive Audit: Scans the entire repository for various forms of dead code.
False Positive Mitigation: Includes a verification phase to avoid incorrectly flagging essential code.
Risk-Based Triage: Prioritizes findings by risk level (High, Medium, Low) for efficient cleanup.
Structured Reporting: Generates a detailed DEAD-CODE.md report with findings, a cleanup roadmap, and an executive summary.
Use Case: A developer can run this skill before a major refactor to understand exactly which parts of the codebase can be safely removed, reducing maintenance overhead and improving performance.

Quick Start

Run the dead-code skill to perform a full codebase analysis and generate a report.

Frequently Asked Questions about dead-code

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

FAQPage Schema

How do I identify dead code and unused declarations in my codebase?▼

A comprehensive dead code audit scans your entire repository to detect unreachable declarations, dead control flow, and phantom dependencies. It produces a risk-ranked report with a cleanup roadmap to systematically reduce technical debt.

What is the best way to audit technical debt before a major refactoring?▼

Auditing technical debt before refactoring involves analyzing the codebase to identify unused code and phantom dependencies. This generates a structured report with a cleanup roadmap, detailing exactly which parts can be safely removed to lower maintenance overhead.

How does a dead code analysis tool prevent false positives?▼

Dead code analysis prevents false positives by including a verification phase before finalizing results. This ensures essential code is not incorrectly flagged, providing a reliable, risk-based triage of high, medium, and low findings for safe elimination.

Can I get a risk-based triage for unreachable code removal?▼

Risk-based triage for unreachable code removal categorizes findings into high, medium, and low risk levels. This prioritization allows you to address the most critical technical debt first, guided by a structured cleanup roadmap and executive summary.

What format does a code audit report use for tracking unused code?▼

A code audit report for unused code uses a structured Markdown format, specifically generating a DEAD-CODE.md file. This document includes detailed findings, a cleanup roadmap, and an executive summary to guide maintainability improvements.