dead-code | dead-code | ClaudePluginHub

Skill

Community

dead-code

0

Description

Find and remove unused code added in the current branch. Use when asked to find dead code, remove unused functions, clean up unreferenced code, or check for orphaned controllers/services/SDK functions. Triggers on phrases like "find dead code", "remove unused code", "check for orphaned functions", or "clean up unreferenced exports".

Install

1

Add the repository(one-time)

$

/plugin marketplace add franchiseai/claude-code-plugins

2

Install the plugin

$

/plugin install dead-code@fsai

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Dead Code Removal

Find and remove code added in the current branch that is never actually used.

Workflow

Get the diff: git diff master...HEAD --name-only to find changed files
For each changed file, identify newly added exports:
- Functions, classes, constants, types
- Controllers, services, SDK functions, API endpoints
- React components, hooks, utilities
Search the codebase for references to each new export
Flag exports with zero references (excluding their own definition and re-exports)
Remove confirmed dead code or report findings

What to Look For

Backend dead code

Controllers with no routes pointing to them
Service methods never called by controllers or other services
SDK/API client functions never imported in frontend
Middleware not registered in any route
Database models with no queries

Frontend dead code

Components never rendered or imported
Hooks never called
Utility functions never imported
Context providers never used
Redux actions/selectors with no dispatch/useSelector calls

Shared dead code

Types/interfaces never referenced
Constants never imported
Exported functions only used internally (should not be exported)

Search Strategy

For each new export ExportName:

Grep for import statements: import.*ExportName or require.*ExportName
Grep for direct usage: ExportName( or <ExportName or .ExportName
Check barrel files (index.ts) for re-exports
Exclude the file where it's defined from results

An export is dead if:

Zero imports outside its own file
Zero usages outside its own file
Not re-exported from a public API barrel

Guidelines

Only analyze code added in the current branch (not pre-existing code)
Be careful with dynamically referenced code (string-based imports, reflection)
Check for indirect usage through barrel files and re-exports
When uncertain, report as "potentially unused" rather than auto-deleting
Preserve code that's part of a public API even if unused internally
Report a summary: number of dead exports found, files affected, bytes removed

Links

GitHub Stats

0 forks

Similar Skills

claude-opus-4-5-migration

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

claude-opus-4-5-migration

47.1k

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

frontend-design

47.1k

Writing Hookify Rules

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

47.1k