dead-code

What it does and when to use it

Use this skill to detect and clean up dead code in this repo, starting with the project’s TypeScript dead-code scripts and validating that removals do not regress behavior.

How it works

1. Workflow
2. Repo Rules
3. Typical Validation

---
name: dead-code
description: Use this skill to detect and clean up dead code in this repo, starting with the project’s TypeScript dead-code scripts and validating that removals do not regress behavior.
---

# 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.

## 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 --run-unit-lane` when test changes may affect the 100ms expectation, or pass an existing focused JUnit XML report to measure it directly

Versions

Database snapshot: 13.11.2026 · package version 020ed5693bec (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100refactor-clean
  Use when code has grown complex, duplicated, or cluttered — clean up structure and remove dead code without changing observable behavior
• 100run-ts-cleanup
  Use if cleaning up a TypeScript codebase — dead code, unused deps, AI slop, weak types.
• 100code-dead-code
  Detect dead code, unused exports, unreachable branches, and orphaned files. Use when reducing maintenance burden, cleaning up after refactors, or auditing codebase health.
• 100sweeping-dead-code
  Use when the user explicitly asks to find, list, audit, or sweep unused or dead code across a path, the repository, or a branch. Reports only and never edits code. Do NOT activate during implementation work; writing-code handles code an edit orphans.
• 100clean-up
  Use when the user asks to clean up code without changing behaviour: dead code, import cycles, deprecated APIs, lint warnings, tidying a module. Triggers include "clean up", "remove dead code", "tidy this module", "fix lint warnings", "replace deprecated APIs", "refactor without changing behaviour".
• 100fai-dead-code-removal
  Identify and remove dead code in Python/TypeScript — unused exports, unreachable branches, and orphaned files, verified by tooling. Use this skill when cleaning up a codebase, reducing bundle size, or before a refactor — even if the user only says "remove unused code".