Slash Command

/SKILL

Detects and removes dead code in the repo using TypeScript scripts, reviews candidates in context, cleans in small batches, and validates with lint/build/test to prevent regressions.

Typescript

Bun

Bash

code-quality

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

Details

Namespacedead-code/

Prompt Preview

# Dead Code

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

## Workflow

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

#...

Command Content

Other plugins with /SKILL

/refactor-clean

173.8k

Safely detects and removes dead code using project-specific analysis tools, verifies each deletion with full test suite runs, and produces a cleanup summary.

everything-claude-code

/refactor-clean

149

Safely identifies dead code using analysis tools, removes safe items with test verification at each step, handles risky ones cautiously, and reports cleanup summary.

awesome-claude-notes

/dead-code

1.4k

Finds and removes dead code: unused imports/exports, unreachable code, dead feature flags. Uses TypeScript/ESLint/Python(Ruff)/Go linters; verifies with tests/build.

claude-code-toolkit

/find-dead-code

1.0k

Scans codebase for dead code like unused exports, files, variables, unreachable code, and long comments. Builds dependency graph from entry points and generates sorted report with confidence levels and totals.

dead-code-finder

/refactor-clean

681

Safely identifies dead code using knip, depcheck, ts-prune; generates analysis report; removes safe items after test verification and shows cleanup summary.

claude-forge

/clean

119

Analyzes recent changes in commit range, unstaged files, or context for dead code, orphaned artifacts from failed branches; generates validated cleanup tasks and reports.

spectre

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

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