ln-626-dead-code-auditor

Detect dead-code patterns and generate a markdown findings report.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-626-dead-code-auditor-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-626-dead-code-auditor
Source: https://github.com/0xtaoist/taogate/tree/main/ln-626-dead-code-auditor
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-626-dead-code-auditor-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checks for unreachable code, unused imports/variables/functions, and legacy shims to improve maintainability.

Core Features & Use Cases

  • Unreachable code detection via lint rules and grep scans.
  • Detection of unused imports, variables, and functions across multi-language codebases.
  • Identification of commented-out code and deprecated patterns with remediation guidance.
  • Legacy shim and backward-compatibility review to reduce hidden risks.
  • Generates a consolidated markdown findings report for risk triage.

Quick Start

Run the dead-code-auditor against your repository to produce a markdown findings report at the designated output directory.

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 detect dead code and unreachable branches in a monorepo?

Dead code detection scans your monorepo to identify unreachable branches, unused imports, and legacy shims. It applies lint rules and grep scans across supported ecosystems to produce a structured markdown report with severities and remediation guidance.

What is the best way to find unused variables and legacy shims across JavaScript and Python codebases?

The best way to find unused variables and legacy shims across JavaScript and Python codebases is to use static analysis. This approach detects unused functions and backward-compatibility patterns, reducing hidden risks while generating a consolidated findings report for triage.

Can I use static analysis to scan multi-language projects for commented-out code?

Yes, you can use static analysis to scan multi-language projects for commented-out code. The scanner identifies deprecated patterns and unreachable code across supported ecosystems like JavaScript, TypeScript, and Python, providing remediation guidance in a markdown report.

Does dead code auditing work for large monorepos with mixed JavaScript and Python ecosystems?

Yes, dead code auditing works for large monorepos with mixed JavaScript, TypeScript, and Python ecosystems. It applies lint rules and grep scans to detect unreachable code and legacy shims, generating a consolidated markdown report for risk triage.

What are the limitations of lint rules when identifying unreachable code and deprecated patterns?

Lint rules for identifying unreachable code and deprecated patterns are limited to static analysis without runtime execution context. They may miss dynamically called legacy shims or conditionally executed branches, so use the generated markdown report to triage findings manually.