find-dead-codelisted

# Find Dead Code Surface candidates. Never delete. The user verifies and removes. ## Rules 1. **Detect and report only.** Do not run `rm`, `git rm`, or edit imports as part of this skill. 2. **A candidate is a hypothesis, not a verdict.** Every candidate ships with the verification recipe below; the user runs the final eye. 3. **Scope before running.** Ask the user which area: a single module, package, or service, or the whole repo. Repo-wide scans are slow and noisy; one subsystem at a time produces actionable lists. 4. **Follow the project's writing conventions in the output.** ## Detectors Prefer a language-appropriate detector when the project already configures one (check the repo root and the project's lint config); fall back to grep otherwise. Examples by ecosystem: - **JS / TS:** `knip`, `ts-prune`, `unimported`. - **Python:** `vulture`, `ruff` unused-code rules (`F401`, `F841`). - **Go:** `staticcheck` (`U1000`), `deadcode`. - **Rust:** compiler `dead_code` warnings (`cargo check`), `cargo-udeps` for unused dependencies. - **JVM:** IDE / `detekt` / `PMD` unused-code inspections. Never install a detector the project does not already use; say which one would help and let the user decide. Detector output is a starting list, not a verdict: every survivor still goes through the verification recipe. ## Categories Pick the category the user asked about, or run all four if they said "find dead code" with no scope. ### A. Unreferenced files Source files (in the pro