dead-code-cleanup

Identify and remove dead code in Repowise-indexed codebases with risk checks.

5.0k|548|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/repowise-dev/repowise --skill dead-code-cleanup-repowise-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-code-cleanup
Source: https://github.com/repowise-dev/repowise/tree/main/plugins/claude-code/skills/dead-code-cleanup
Command: npx skills add https://github.com/repowise-dev/repowise --skill dead-code-cleanup-repowise-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and remove dead or unused code in a Repowise-indexed repository, reducing maintenance effort and the risk of stale code paths.

Core Features & Use Cases

  • Dead code detection: Find unreachable files, unused exports, and orphan packages across monorepos.
  • Risk-aware cleanup: Validate deletions with risk checks before removing any code.
  • Use Case: When cleaning a large repository, run get_dead_code() to surface candidates and then verify with get_risk() before deletion.

Quick Start

Run a dead-code scan with the Repowise agent to surface safe-to-delete findings.

Frequently Asked Questions about dead-code-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and remove dead code in a large repository?

Dead code cleanup scans indexed codebases to identify unreachable files, unused exports, and zombie packages, then performs risk checks to surface only safe-to-delete candidates for removal.

What does dead code detection look for in a monorepo?

Dead code detection in monorepos targets unreachable files, unused exports, and orphan packages across multiple repositories to reduce maintenance effort and eliminate stale code paths.

Can I safely delete unused exports and zombie packages without breaking dependencies?

Yes, risk-aware cleanup validates potential deletions by verifying dependencies with risk checks before removing any code, ensuring only safe-to-delete candidates are surfaced for deletion.

Do I need a Repowise-indexed codebase to run dead code analysis?

Yes, dead code cleanup operates on Repowise-indexed repositories, using get_dead_code() to fetch findings and get_risk() to verify dependencies before any deletion occurs.

What's the best way to reduce maintenance burden from stale code paths?

Running a dead code scan with risk-aware cleanup identifies unreachable files and unused exports, then verifies dependencies before deletion to safely reduce maintenance burden.