kill-dead-code
Find and remove unreachable/unused code safely. Use during cleanup or before a refactor.
Works with
Agent Skills format with YAML frontmatter. Claude Code reads it as-is.
--- name: "kill-dead-code" description: "Find and remove unreachable/unused code safely. Use during cleanup or before a refactor." license: "MIT" --- # 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.
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
