audit-dead

Audit code changes for dead imports, parameters, and schema gaps.

15|6|Updated May 7, 2026

Search Tags:#documentation #audit #static-analysis #code-refactor #dead-import #dead-parameter #schema-gap

Ready to run

npx skills add https://github.com/MinhThang1009/dotclaude --skill audit-dead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-dead
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/plan-workflow/skills/audit-dead
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill audit-dead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill audits code changes to identify dead imports, dead parameters, and broader maintenance gaps that emerge after refactoring, preventing silent regressions.

Core Features & Use Cases

Dead Import Scan: detect symbols imported but never used in the file body.
Dead Parameter Cascade: trace removed parameters through callers to expose dead data flow.
Schema Consistency Across Parallel Paths: ensure fields are present across happy and fallback paths.
Documentation Staleness: surface outdated references in CLAUDE.md or JSDoc.
Structural Misplacement: identify module-level helpers that belong as class static methods.
Unreachable Code: flag code behind unconditional returns or throws.

Quick Start

Run the audit tool on your changed codebase to surface all dead imports, dead parameters, schema gaps, and unreachable code.

Frequently Asked Questions about audit-dead

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

FAQPage Schema

How do I detect dead imports and dead parameters after a code refactor?▼

You can detect dead imports and dead parameters by running a static analysis audit on your refactored codebase to trace removed parameters through callers and flag unused imported symbols.

What is dead code cascading and how does it happen during refactoring?▼

Dead code cascading occurs when parameter removal leaves dependent callers and downstream logic intact. Static analysis audits trace these removed parameters through callers to expose dead data flow and prevent silent regressions.

How do I check schema consistency across happy and fallback paths after batch changes?▼

Schema consistency is checked by enforcing audits that ensure required fields remain present across both happy and fallback execution paths, preventing schema gaps during batch changes.

Can static analysis detect outdated documentation and misplaced module-level helpers?▼

Static analysis detects outdated documentation by surfacing stale references in CLAUDE.md or JSDoc, and identifies structural misplacement by flagging module-level helpers that belong as class static methods.

What is the best way to find unreachable code behind unconditional returns or throws?▼

The best way to find unreachable code is to run an audit that flags any logic placed behind unconditional returns or throw statements, surfacing dead segments for removal.

When do I need to run a dead code audit in the plan-refactor workflow?▼

A dead code audit is needed during Phase 7 of the plan-refactor workflow and after batch changes to validate that modifications introduce no dead imports, dead parameters, or schema gaps.