ln-626-dead-code-auditor

Audit codebases for dead code, unused assets, and legacy patterns.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-626-dead-code-auditor-mcauduro0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-626-dead-code-auditor
Source: https://github.com/mcauduro0/Macro_Trading/tree/main/.claude/skills/ln-626-dead-code-auditor
Command: npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-626-dead-code-auditor-mcauduro0

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies and reports on various forms of dead code, unused assets, and outdated patterns within a codebase, helping to improve code quality and maintainability.

Core Features & Use Cases

  • Dead Code Detection: Finds unreachable code, unused imports, variables, and functions.
  • Legacy Audit: Identifies commented-out code, backward compatibility shims, and deprecated patterns.
  • Compliance Scoring: Calculates a compliance score based on audit findings.
  • Use Case: A development team can use this Skill to perform a quarterly audit of their main application codebase, identifying areas for refactoring and cleanup to reduce technical debt.

Quick Start

Run the ln-626-dead-code-auditor skill to audit the codebase located at /path/to/your/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 dead code and unused imports in my codebase?

Auditing legacy code for refactoring targets involves identifying commented-out code, backward compatibility shims, and deprecated patterns. This Skill categorizes these outdated elements within your codebase, helping development teams pinpoint specific areas requiring cleanup and modernization during quarterly reviews.

How does a dead code audit calculate compliance scores for technical debt?

A dead code audit calculates a compliance score based on the volume and severity of findings like unreachable code and unused variables. This scoring mechanism quantifies your codebase's health, providing a measurable baseline for tracking code quality improvements over time.

Can I use this dead code auditor on any software engineering project?

You can use this dead code auditor on any software engineering project by running it against your project directory. It requires no external dependencies, applying linters and pattern matching to analyze your code structure regardless of the specific framework.

What is the best way to identify unused assets and unreachable functions during refactoring?

The best way to identify unused assets and unreachable functions during refactoring is through pattern matching and lint analysis. This Skill examines import statements, variable usage, and commented sections to accurately detect and categorize unused functions within legacy codebases.