Skill

dead-code

Detects and removes dead TypeScript code using repo scripts like detect-dead-code-ts.sh, reviews in context, and validates with lint, build, tests to prevent regressions.

Typescript

Bash

Bun

code-quality

npx claudepluginhub kaeawc/auto-mobile --plugin auto-mobile

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this when the user wants dead-code analysis or cleanup.

SKILL.md

Similar Skills

dead-code-detector

Detects unused functions, imports, unreachable code in Python (vulture), TypeScript (knip), Rust (cargo clippy) codebases for cleanup and refactoring.

4 files5 tools

quality-tools

dead-code-detector

Identifies unused imports, variables, functions, unreachable code, dependencies, and CSS for safe removal. Generates reports categorizing safe-to-remove, potentially unused, and review-required items.

devkit

configure-dead-code

Checks and configures dead code detection tools: Knip (JS/TS), Vulture/deadcode (Python), cargo-machete (Rust). Audits setups, migrates tools, adds to CI/CD pipelines, standardizes monorepos.

1 file10 tools

configure-plugin

Stats

Stars34

Forks0

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Dead Code

Use this when the user wants dead-code analysis or cleanup.

Workflow

Start with detection, not deletion.

For TypeScript, run bash scripts/detect-dead-code-ts.sh, optionally writing reports to scratch/dead-code/.

Review each candidate in full context before removing it. Unused exports in tooling output are often false positives.

Check callers, tests, generated code, and dynamic entry points before deleting anything.

Remove dead code in small batches so regressions are easy to isolate.

Re-run the detector and the relevant validation after each batch.

Repo Rules

Prefer repo scripts and bun tasks over ad hoc dead-code tools.

Treat package.json dependency findings as suggestions until confirmed.

Do not remove code referenced by reflection, CLI wiring, generated schemas, MCP registration, or platform build files without proof.

Validate behavior after cleanup with the narrowest relevant commands.

Typical Validation

bun run lint

bun run build

bun test

bash scripts/validate-bun-test-timings.sh when test changes may affect the 100ms expectation

Dead Code

Use this when the user wants dead-code analysis or cleanup.

Workflow

Start with detection, not deletion.
For TypeScript, run bash scripts/detect-dead-code-ts.sh, optionally writing reports to scratch/dead-code/.
Review each candidate in full context before removing it. Unused exports in tooling output are often false positives.
Check callers, tests, generated code, and dynamic entry points before deleting anything.
Remove dead code in small batches so regressions are easy to isolate.
Re-run the detector and the relevant validation after each batch.

Repo Rules

Prefer repo scripts and bun tasks over ad hoc dead-code tools.
Treat package.json dependency findings as suggestions until confirmed.
Do not remove code referenced by reflection, CLI wiring, generated schemas, MCP registration, or platform build files without proof.
Validate behavior after cleanup with the narrowest relevant commands.

Typical Validation

bun run lint
bun run build
bun test
bash scripts/validate-bun-test-timings.sh when test changes may affect the 100ms expectation