mcpbeat

Dead Code

parcadei/dead-code

Find unused functions and dead code in the codebase

423 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3880
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill dead-code

The instruction itself

7 sections, as written by the author

Dead 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 points
  • test_*, *_test - Test functions
  • setup, 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 |

# Impact analysis (who calls this?)
tldr impact func_name .

# Architecture layers
tldr arch src/

# Full codebase structure
tldr structure . --lang python

How to use it

Copy the folder

Take parcadei/dead-code from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.