dead-check

Detect dead code and orphaned files across multiple programming languages.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill dead-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-check
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/ccc/skills/dead-check
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill dead-check

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Dead code accumulates in codebases, making maintenance harder and increasing risk of bugs. This Skill enforces dead code elimination by detecting commented-out code, unused exports, orphaned files, unlinked TODOs, and stub/placeholder functions to keep the project healthy and safe for refactors.

Core Features & Use Cases

  • Dead Code Detection: identify and surface commented-out blocks and non-functional stubs.
  • Public API Hygiene: flag unused exports to keep APIs minimal and maintainable.
  • Project Hygiene: surface orphaned files and untracked TODOs with issue references.
  • Refactor Guidance: provide actionable steps to clean up code with minimal disruption.

Quick Start

Run a targeted scan of your scope to locate cleanup opportunities and recommended actions.

Frequently Asked Questions about dead-check

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

FAQPage Schema
How do I find and remove dead code in a TypeScript or Python project?

Dead code detection works by analyzing your codebase exports, tracking orphaned files, and identifying non-functional placeholders like stubs. It flags unused exports and commented-out blocks to keep your API minimal and reduce maintenance risks during refactors.

Can I use static analysis to track unlinked TODOs and orphaned files?

Yes, static analysis can surface unlinked TODOs and orphaned files across your codebase. It tracks unlinked TODOs and recommends converting them into issue references, while flagging orphaned files for deletion to maintain project hygiene.

Does dead code elimination work with Go and Rust codebases?

Yes, dead code elimination works with Go and Rust codebases, alongside TypeScript, JavaScript, and Python. It analyzes exports, orphaned files, and non-functional placeholders across these languages to keep libraries, CLI tools, services, and test suites healthy.

What is the best way to clean up unused exports and stub functions?

The best way to clean up unused exports and stub functions is to use an automated linter script that detects non-functional placeholders and flags unused API endpoints, providing actionable refactor guidance to delete stubs with minimal disruption.

When should I run a dead code scan before a major project refactor?

You should run a dead code scan before a major refactor to eliminate commented-out blocks, unused exports, and orphaned files. Removing this non-functional code reduces bug risks and makes the remaining architecture safer to modify.