# Kill Dead Code

Find and remove unreachable/unused code safely.

- Repository: https://github.com/Archive228/loopkit (756 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-07-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Archive228/loopkit --skill kill-dead-code -g -a claude-code -y`
Codex: `npx skills add Archive228/loopkit --skill kill-dead-code -g -a codex -y`
Cursor: `npx skills add Archive228/loopkit --skill kill-dead-code -g -a cursor -y`
Gemini CLI: `npx skills add Archive228/loopkit --skill kill-dead-code -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Archive228/loopkit`

## Description

Find and remove unreachable/unused code safely. Use during cleanup or before a refactor.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Kill Dead Code
1. **Prove it's dead**, no references (grep the symbol across the repo, including dynamic/string usage and tests). Unused export ≠ dead if it's a public API.
2. Check it's not feature-flagged off (dead today, alive when the flag flips).
3. Delete it AND its now-orphaned tests, imports, and config.
4. Run the full suite + a build. Dead code removal should change behavior in exactly zero ways.
Bias to delete: every line someone has to read is a cost. But never delete what you can't prove is unreachable, say "I think X is unused, confirm?" instead of guessing.

