Skip to content
Development
Skill

/dead-code-cleanup

Use when the user asks about cleanup, removing unused code, refactoring, reducing bundle size, or identifying dead code in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when discussing technical debt, code hygiene, or repository maintenance.

From plugin
repowise
8.1k8 skills17 commands1 MCP

Claude Code

$ npx -y skills add repowise-dev/repowise --skill dead-code-cleanup --agent claude-code

SKILL.md

dead-code-cleanup.SKILL.md
name: dead-code-cleanup
description: >
  Use when the user asks about cleanup, removing unused code, refactoring, reducing bundle size,
  or identifying dead code in a Repowise-indexed codebase (.repowise/ directory exists). Also
  activates when discussing technical debt, code hygiene, or repository maintenance.
user-invocable: false

Dead Code Cleanup with Repowise

Repowise detects dead code through graph analysis — no LLM needed, works even with a template-rendered wiki.

When the user asks about dead/unused code

Call `get_dead_code()` to get findings sorted by confidence tier. Useful parameters:

  • `safe_only=true` — only findings confirmed safe to delete (confidence >= 0.7)
  • `kind="unreachable_file"` — files with no importers
  • `kind="unused_export"` — public symbols nobody uses
  • `kind="zombie_package"` — monorepo packages with no consumers
  • `directory="src/old/"` — limit to a specific directory
  • `tier="high"` — only high-confidence findings (>= 0.8)
  • `min_confidence=0.7` — raise the floor (default is 0.5) for a release-ready cleanup
  • `group_by="directory"` or `group_by="owner"` — roll up to see where the dead code concentrates and who owns the most of it

How to present findings

  • Only suggest deletion for findings with `safe_to_delete: true`
  • For lower-confidence findings, present them as "candidates to investigate" not "things to delete"
  • Dynamically-loaded code (plugins, handlers, adapters) may appear as dead code but isn't — Repowise filters common patterns but edge cases exist

Before deleting anything

1. Confirm with the user. Present the file/symbol name, confidence score, and why Repowise thinks it's dead. 2. Call `get_risk(targets=["path/to/file"])` to double-check dependents. 3. Recently-modified "dead" code is more likely a false positive — flag this if the finding has recent git activity.

Safe deletion order

1. Unreachable files first (whole file removal, cleanest) 2. Unused internal symbols next 3. Unused exports last (highest false-positive risk due to potential dynamic imports)

Read more
@repowise-dev
Ships withrepowise

Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

8.1k8 skills1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
8.1k
Star history of repowise-dev/repowise on GitHub, a chart by star-history.com

Other skills on repowise.

change-review

change-review

Use when reviewing a set of changes before they merge — a PR, a branch diff, or the working-tree changes you just made — in a…

code-health

code-health

Use when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain,…

codebase-exploration

codebase-exploration

Use when exploring, understanding, or answering questions about a codebase that has Repowise indexed (a .repowise/ directory in…

pre-modification

pre-modification

Use before modifying, refactoring, or deleting files in a codebase that has Repowise indexed (indicated by a .repowise/…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about dead-code-cleanup.

Which coding agents can use dead-code-cleanup?
dead-code-cleanup installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.