Dead Code
- 634 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
dead-code is a Claude skill that runs on-demand TLDR dead-code analysis to list unused functions for developers preparing refactors or release review across Python and TypeScript codebases.
About
dead-code is a continuous-claude-v3 skill that finds unused functions and unreachable code using TLDR static analysis via Bash. Developers run commands such as tldr dead ., tldr dead src/, or tldr dead . --lang python with optional --entry flags to exclude main, cli, or test entry points. Output reports total functions, dead function counts, and file-line locations like old_helper (src/utils.py:42). Reach for dead-code before large refactors or release review when you need an evidence-backed list of candidates to delete rather than manual grep guessing.
- Runs `tldr dead` for project-wide or directory-scoped unused function detection
- Supports `--entry` patterns to exclude main, CLI, tests, and framework route handlers
- `--lang python` and `--lang typescript` for language-targeted scans
- Cross-platform Bash workflow (Windows PowerShell, Mac, Linux, WSL)
- On-demand replacement for slower automatic session-start dead-code hooks
Dead Code by the numbers
- 634 all-time installs (skills.sh)
- +9 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #205 of 1,382 Code Review & Quality skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill dead-codeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 634 |
|---|---|
| repo stars | ★ 3.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you find unused functions in a codebase?
Run on-demand TLDR dead-code analysis to list unused functions before refactors or release review.
Who is it for?
Developers running pre-refactor or pre-release cleanup who want TLDR static analysis output for Python or TypeScript repos.
Skip if: Codebases where dynamic reflection, plugin loading, or string-based imports make static reachability analysis unreliable without custom entry points.
When should I use this skill?
A developer asks to find dead code, unused functions, unreachable helpers, or run tldr dead before refactor or release review.
What you get
TLDR dead-code report listing unused functions with file paths, line numbers, and totals
- dead-code analysis report
- unused function list
Files
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 typescriptOutput 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_jobIntegration
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 pythonRelated skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.531k185k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.260k92.5kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.233k185kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.210k92.5k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.178k260kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.167k185kFAQ
What command does the dead-code skill use?
The dead-code skill invokes TLDR through Bash, typically tldr dead . or tldr dead src/. Developers can pass --lang python or --lang typescript and --entry to exclude functions like main or test_ from analysis.
What output does dead-code produce?
dead-code reports total functions, dead function counts, and a list of unused symbols with file paths and line numbers. Example output includes entries such as old_helper (src/utils.py:42) for targeted removal.
Is Dead Code safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.