Dead Code Skill for Claude
Find unused functions and dead code in the codebase
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill dead-codeThe instruction itself
7 sections, as written by the authorDead Code Detection
Find unused functions and dead code using TLDR static analysis.
Quick Start
# Scan entire project
tldr dead .
# Scan specific directory
tldr dead src/
# Specify entry points (functions to exclude from analysis)
tldr dead . --entry main cli test_
# Specify language
tldr dead . --lang python
tldr dead . --lang typescript
Output Format
Dead code analysis:
Total functions: 150
Dead functions: 12
Unused functions:
- old_helper (src/utils.py:42)
- deprecated_func (src/legacy.py:15)
- _unused_method (src/api.py:230)
Cross-Platform
Works on Windows, Mac, and Linux (including WSL).
# Windows (PowerShell)
tldr dead .
# Mac/Linux
tldr dead .
Entry Points
Functions matching entry patterns are excluded from dead code analysis:
main,cli- Application entry pointstest_*,*_test- Test functionssetup,teardown- Fixtures@app.route,@api.endpoint- Framework handlers
# Custom entry points
tldr dead src/ --entry main api_handler background_job
Integration
This skill replaces the session-start-dead-code hook with on-demand analysis.
| Approach | Pros | Cons |
|----------|------|------|
| Hook (removed) | Automatic | Slowed startup by 3s |
| Skill (this) | On-demand, fast | Manual invocation |
Related Commands
# Impact analysis (who calls this?)
tldr impact func_name .
# Architecture layers
tldr arch src/
# Full codebase structure
tldr structure . --lang python
Other skills for the same job
different authors, same section of the catalogue
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
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.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
How to use it
Take parcadei/dead-code from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.