Dead Code Finder

Identify unreferenced code and orphan modules in monorepos.

1|1|Updated Mar 31, 2026

Search Tags:#safety #cleanup #monorepo #code-analysis #references #dead-code

Ready to run

npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill dead-code-finder-btabaska

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Dead Code Finder
Source: https://github.com/btabaska/simpler-grants-documentation-automation/tree/main/.cursor/skills/skill-dead-code-finder
Command: npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill dead-code-finder-btabaska

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Dead Code Finder identifies unreferenced exports, unused React components, orphaned Python modules, and stale test fixtures in a monorepo, providing a safe candidate list with evidence trails to guide cleanup.

Core Features & Use Cases

Evidence-backed candidate listing: reports file paths, symbols, and last-touched git info for each potential dead code item.
Reference-aware filtering: filters out items referenced by dynamic imports or gated by feature flags (where applicable).
Safe cleanup guidance: ranks candidates by confidence and includes actionable remediation notes to avoid accidental deletions.

Quick Start

Simply run the dead code finder to generate a candidates report for the target scope (frontend/api/all) and review high-confidence items before cleanup.

Frequently Asked Questions about Dead Code Finder

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

FAQPage Schema

How do I find unreferenced exports and unused React components in a monorepo?▼

To identify unreferenced exports and unused React components in a monorepo, use a dead code finder that generates an evidence-backed candidate list with file paths, symbols, and inbound references for safe review.

Can I detect orphaned Python modules and stale test fixtures before a release?▼

Yes, you can detect orphaned Python modules and stale test fixtures during pre-release hygiene checks by running a dead code finder to surface candidates ranked by confidence with last-touched git information.

What is the safest way to clean up dead code without breaking dynamic imports?▼

The safest way to clean up dead code without breaking dynamic imports is to use reference-aware filtering that excludes items gated by feature flags, ensuring the tool only reports candidates and never deletes code automatically.

Does dead code analysis work across frontend and backend components in a monorepo?▼

Dead code analysis works across frontend and backend components in a monorepo by targeting specific scopes like frontend, API, or all, generating a bounded candidate report with path and symbol evidence for each component.

How do I review stale fixtures and orphan modules without accidentally deleting used code?▼

To review stale fixtures and orphan modules without accidental deletions, use a dead code finder that ranks candidates by confidence and includes actionable remediation notes with evidence trails rather than auto-deleting files.