architectural-decision…
Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns, restructuring, choosing between…
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.
$ npx -y skills add repowise-dev/repowise --skill dead-code-cleanup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/dead-code-cleanupContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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
Repowise detects dead code through graph analysis — no LLM needed, works even with a template-rendered wiki.
Call `get_dead_code()` to get findings sorted by confidence tier. Useful parameters:
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.
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)
Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Repo: repowise-dev/repowise
Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns, restructuring, choosing between…
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 Repowise-indexed codebase…
Use when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain, what to refactor next, untested…
Use when exploring, understanding, or answering questions about a codebase that has Repowise indexed (a .repowise/ directory in the project root). Activates…
Use before modifying, refactoring, or deleting files in a codebase that has Repowise indexed (indicated by a .repowise/ directory). Activates when Claude is…
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files…