dead-code-auditlisted

# Dead Code Audit ## Core Rule Confirm code is unreachable across the full call graph before flagging. Never remove code without explicit user approval, even for obvious dead branches. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections (Top Rules + index) If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/dead-code-audit` when: - Codebase has grown organically and likely contains unused code - After a major feature removal or refactoring - Before a codebase migration to minimize what gets carried over - During tech debt reduction sprints - Preparing for a code quality review or due diligence ## Default Behavior When the user asks to audit, scan, review, or "give me a report" for dead code / unused code, produce the full dead-code-audit report automatically using the Process and Output Format sections below. Do not require the user to specify fields. Only modify files when the user explicitly requests implement / fix / apply / refactor. By default, this skill is **report-only**. ## Scope Rules - Analyze ONLY the files and directories relevant to this skill's purpose - Do not refactor, fix, or modify code — this is a read-only analysis unless explicitly stated otherwise - Log unrelated issues f