ln-626-dead-code-auditor

Audit codebases for unreachable code, unused imports, variables, functions, and deprecated patterns.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-626-dead-code-auditor-dorrio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-626-dead-code-auditor
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-626-dead-code-auditor
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-626-dead-code-auditor-dorrio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and reports on various forms of dead or unused code within a project, helping to streamline the codebase and reduce maintenance overhead.

Core Features & Use Cases

  • Unreachable Code Detection: Finds code paths that can never be executed.
  • Unused Element Identification: Locates unused imports, variables, functions, and methods.
  • Commented-Out Code Removal: Flags code that has been commented out, which may be obsolete.
  • Deprecated Pattern Detection: Identifies outdated coding practices that should be updated.
  • Use Case: A developer can use this skill to clean up a large, legacy codebase before a major refactor, ensuring that only active and necessary code remains.

Quick Start

Run the dead code auditor to find all unused imports and variables in the current project.

Frequently Asked Questions about ln-626-dead-code-auditor

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

FAQPage Schema
How do I find unused imports and unreachable code in my project?

You can audit your codebase by running a static analysis tool that scans source files to detect and report unreachable code paths, unused imports, variables, and functions. This helps reduce maintenance overhead by identifying obsolete segments.

What is dead code detection and when do I need to audit my codebase?

Dead code detection is the static analysis of source files to identify unreachable code, unused variables, and deprecated patterns. You need to audit your codebase during major refactors or legacy cleanup to ensure only active, necessary code remains.

Can this dead code auditor handle large legacy codebases before refactoring?

Yes, dead code auditing is designed to clean up large legacy codebases before a major refactor. It requires static analysis of the project's source files to accurately identify unused functions, variables, and imports across the entire codebase.

What's the best way to identify commented-out code and deprecated patterns?

The best way to identify commented-out code and deprecated patterns is using a dedicated auditing skill that flags obsolete segments during static analysis. This ensures outdated coding practices are detected alongside unused variables for comprehensive code hygiene.

Does detecting unused variables and functions require any external dependencies?

Detecting unused variables and functions requires no external dependencies. The auditing process relies solely on static analysis of the project's existing source files to locate unused imports, variables, functions, and unreachable code segments.