en un clic
dead-code
Find unused functions and dead code in the codebase
Menu
Find unused functions and dead code in the codebase
Afenda metadata-driven EUI polish workflow. Use automatically when implementing, reviewing, or refining governed renderers (packages/governed-surface/src/metadata/renderers), surface builders (packages/kernel/src/modules/list-surfaces.ts), Pattern A/B/C ERP pages, or the dev metadata-renderer-gallery. Composes shadcn-metadata, governed-renderer contracts, and Vercel web-design/composition skills. Do not invoke sibling skills separately for the same task.
Refactor And Fold duplicate Afenda feature areas into a canonical module. Use when the user invokes /raf, asks to merge duplicate system-admin sections, consolidate overlapping routes, or remove a feature folder after folding its unique fields into the surviving area. No redirects unless explicitly requested.
Use when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks (React, Next.js, Drizzle, Tailwind, etc.).
Afenda Ask-Docs Quality Standard workflow. Use automatically when authoring, reviewing, or improving content/ask-docs MDX. Composes documentation-audit (code-verified accuracy) and technical-writing (internal-guide prose) with the six-dimension ADQS rubric. Do not invoke sibling skills separately.
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
| name | dead-code |
| description | Find unused functions and dead code in the codebase |
| allowed-tools | ["Bash"] |
| keywords | ["dead code","unused","cleanup","refactor","unreachable"] |
Find unused functions and dead code using TLDR static analysis.
# 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
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)
Works on Windows, Mac, and Linux (including WSL).
# Windows (PowerShell)
tldr dead .
# Mac/Linux
tldr dead .
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
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