Help us improve
Share bugs, ideas, or general feedback.
From repowise
Analyzes and removes dead code in Repowise-indexed codebases using graph analysis. Suggests safe deletion order and flags false positives.
npx claudepluginhub repowise-dev/repowise --plugin repowiseHow this skill is triggered — by the user, by Claude, or both
Slash command
/repowise:dead-code-cleanupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Repowise detects dead code through graph analysis — no LLM needed, works even in index-only mode.
Diagnoses repo rot prioritizing dead code (HIGH/MEDIUM/LOW confidence), god files, hotspots, hardcoded paths, stale TODOs, lopsided imports. Language-agnostic pure diagnosis.
Finds and safely removes unused exports, dead files, orphaned dependencies, and stale constraints. Use after refactoring or as periodic hygiene.
Detects dead code, unused exports, orphaned files, circular dependencies, unused packages, stale TODOs, and hygiene issues across 11 categories. Use scan, safe, aggressive modes on full codebase or paths.
Share bugs, ideas, or general feedback.
Repowise detects dead code through graph analysis — no LLM needed, works even in index-only mode.
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 importerskind="unused_export" — public symbols nobody useskind="zombie_package" — monorepo packages with no consumersdirectory="src/old/" — limit to a specific directorytier="high" — only high-confidence findings (>= 0.8)min_confidence=0.7 — raise the floor (default is 0.5) for a release-ready cleanupgroup_by="directory" or group_by="owner" — roll up to see where the dead code concentrates and who owns the most of itsafe_to_delete: trueget_risk(targets=["path/to/file"]) to double-check dependents.