ll-find-dead-code

Detect and report deprecated or unreachable code segments in source code repositories.

7|2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-find-dead-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ll-find-dead-code
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/ll-find-dead-code
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-find-dead-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the accumulation of technical debt by identifying deprecated, unused, or dead code paths that clutter the codebase and increase maintenance overhead.

Core Features & Use Cases

  • Static Analysis: Scans the repository to detect functions, classes, or modules that are no longer referenced by the active codebase.
  • Safety Verification: Provides a clear report of identified dead code, allowing developers to review and safely remove bloat without breaking functionality.
  • Use Case: During a major refactoring sprint, use this Skill to audit legacy modules and identify orphaned utility functions that can be safely deleted to improve overall code readability.

Quick Start

Use the ll-find-dead-code skill to scan the current directory and generate a report of all unused functions and classes.

Frequently Asked Questions about ll-find-dead-code

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

FAQPage Schema
How do I find dead code in my codebase?

To find dead code, this Skill performs static analysis on your source code repository to map symbol references and identify orphaned functions, classes, or modules that are no longer reachable by the active codebase.

What is static analysis for identifying unused functions and classes?

Static analysis for identifying unused functions and classes is a scanning process that examines your project structure without executing code, mapping symbol references to accurately detect deprecated or unreachable code segments.

Can I use this dead code detection during a refactoring sprint?

Yes, you can use dead code detection during a refactoring sprint to audit legacy modules, generate a clear report of orphaned utility functions, and safely remove bloat to improve overall code readability.

What is the best way to reduce technical debt from deprecated code paths?

The best way to reduce technical debt from deprecated code paths is to scan your repository to detect unused functions and classes, review the generated safety report, and prune the unreachable code segments to decrease maintenance overhead.

How does this approach verify safety before removing dead code?

This approach verifies safety before removing dead code by generating a clear report of identified orphaned code blocks, allowing developers to review the detected symbol references and safely delete bloat without breaking functionality.

Do I need specific dependencies to scan my directory for orphaned code blocks?

No specific dependencies are required to scan your directory for orphaned code blocks; the Skill operates directly within your software development lifecycle to map project structure and report unused code.