Agent Skills › repowise-dev/repowise › dead-code-cleanup

dead-code-cleanup

GitHub

用于识别和清理代码库中的死代码，支持按置信度、类型过滤，提供安全删除建议及风险评估，辅助技术债治理。

plugins/claude-code/skills/dead-code-cleanup/SKILL.md repowise-dev/repowise

触发场景

用户询问清理无用代码或死代码讨论重构以减少包体积涉及技术债或代码卫生维护

安装

npx skills add repowise-dev/repowise --skill dead-code-cleanup -g -y

更多选项

非标准路径

npx skills add https://github.com/repowise-dev/repowise/tree/main/plugins/claude-code/skills/dead-code-cleanup -g -y

不安装直接使用

npx skills use repowise-dev/repowise@dead-code-cleanup

指定 Agent (Claude Code)

npx skills add repowise-dev/repowise --skill dead-code-cleanup -a claude-code -g -y

安装 repo 全部 skill

npx skills add repowise-dev/repowise --all -g -y

预览 repo 内 skill

npx skills add repowise-dev/repowise --list

SKILL.md

Frontmatter

{
    "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.\n",
    "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

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

Safe deletion order

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