dead-code

Identify unused functions, classes, and dead files across multiple programming languages.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/jcoutsousa/mobile-monorepo-template --skill dead-code-jcoutsousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-code
Source: https://github.com/jcoutsousa/mobile-monorepo-template/tree/main/.github/skills/dead-code
Command: npx skills add https://github.com/jcoutsousa/mobile-monorepo-template --skill dead-code-jcoutsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill detects unused code, functions, classes, and dead files across multiple programming languages, reducing technical debt and improving codebase clarity.

Core Features & Use Cases

  • Unused Function Detection: Finds functions, methods, or classes that are defined but never called or referenced in the project.
  • Dead File Identification: Flags files that are no longer imported, referenced, or utilized in the project, such as obsolete scripts, modules, or components.
  • Use Case: Developers can use this Skill to clean up legacy code in large repositories, streamline their codebases, and optimize build times by removing dead code and unused files.

Quick Start

Run the dead-code trainer on your project directory to scan for and identify unused symbols and files.

Frequently Asked Questions about dead-code

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

FAQPage Schema
How do I find unused functions and dead files in a multi-language codebase?

Finding unused functions and dead files requires static code analysis that cross-references project references to identify unreferenced symbols and obsolete files across your codebase.

Does static analysis for dead code work with Flutter, TypeScript, and Python?

Yes, static analysis for dead code works with Flutter, TypeScript, and Python, as well as Kotlin, Go, Rust, and web frameworks to accurately identify unused functions and classes.

What is the best way to clean up legacy code and reduce technical debt in large repositories?

The best way to clean up legacy code and reduce technical debt is to identify and remove unused code, dead files, and obsolete modules through cross-referenced static analysis.

Can I use code cleanup tools to optimize build times by removing unused classes?

Yes, you can use code cleanup tools to optimize build times by identifying and removing unused classes and dead files that are no longer imported or utilized in your project.

How does cross-referencing project references improve unused code detection accuracy?

Cross-referencing project references improves unused code detection accuracy by ensuring that flagged functions and dead files are truly never called or imported anywhere in the repository.