architectural-decision…
Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns,…
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.
Claude Code
$ npx -y skills add repowise-dev/repowise --skill dead-code-cleanup --agent claude-code
Codex
$ npx skills add repowise-dev/repowise --skill dead-code-cleanup -a codex -y
Cursor
$ npx skills add repowise-dev/repowise --skill dead-code-cleanup -a cursor -y
Gemini CLI
$ npx skills add repowise-dev/repowise --skill dead-code-cleanup -a gemini-cli -y
GitHub Copilot
$ npx skills add repowise-dev/repowise --skill dead-code-cleanup -a github-copilot -y
OpenCode
$ npx skills add repowise-dev/repowise --skill dead-code-cleanup -a opencode -y
Windsurf
$ npx skills add repowise-dev/repowise --skill dead-code-cleanup -a windsurf -y
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.
Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns,…
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…
Use when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain,…
Use when exploring, understanding, or answering questions about a codebase that has Repowise indexed (a .repowise/ directory in…
Use before modifying, refactoring, or deleting files in a codebase that has Repowise indexed (indicated by a .repowise/…
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.