review-dead-code

Identify dead code and generate a removal plan for codebases.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-dead-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-dead-code
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/review-dead-code
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill review-dead-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and plans the removal of obsolete code, such as unused functions, variables, and unreachable code paths, to improve codebase maintainability and reduce technical debt.

Core Features & Use Cases

  • Dead Code Identification: Detects functions, variables, and code blocks that are no longer in use.
  • Systematic Auditing: Employs a structured methodology to ensure thoroughness in code review.
  • Removal Planning: Generates a clear, actionable plan for code removal, prioritizing safety and impact.
  • Use Case: A developer can use this Skill to clean up a legacy codebase, ensuring that only active and necessary code remains, thereby reducing complexity and potential bugs.

Quick Start

Enter planning mode to systematically audit the codebase for dead code and write a removal plan.

Frequently Asked Questions about review-dead-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and remove dead code in a legacy codebase?

Dead code detection identifies unused functions, unread variables, and unreachable code paths within a codebase. This Skill uses specialized query tools to verify global variable ownership and caller lists, ensuring accurate identification before planning removal.

What is the best way to audit for unused functions and unreachable code paths?

Auditing for unused functions requires a structured methodology to ensure thoroughness during code review. This Skill generates an actionable removal plan that prioritizes safety and impact, improving codebase maintainability by systematically targeting obsolete code.

Can I plan technical debt refactoring without accidentally removing active code?

Refactoring technical debt safely requires authoritative caller lists and global variable ownership checks. This Skill utilizes specialized query tools to verify dependencies, ensuring that only truly obsolete functions and unread variables are targeted for removal.

Does this dead code identification approach work for complex codebases with global variables?

Dead code identification in complex codebases requires verifying global variable ownership and caller lists. This Skill employs specialized query tools to accurately detect unread variables and unreachable paths, ensuring thoroughness regardless of codebase complexity.

What are the limitations of automated dead code detection and removal planning?

Automated dead code detection relies on specialized query tools for authoritative caller lists and global variable ownership. Limitations include the need for a structured methodology to ensure thoroughness, as complex dependencies may require manual verification before removal.