dead-code-auditlisted

# Dead Code Audit ultrathink <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/audits/`. > Run `mkdir -p .anthril/audits` before the first `Write` call. > Primary artefact: `.anthril/audits/dead-code-audit.md`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. ## Before You Start 1. **Locate the target.** Use `$ARGUMENTS` if provided, otherwise the current working directory. If neither resolves to a real directory, ask the user for the target path before continuing. 2. **Detect the stack.** Run `scripts/detect-stack.sh` to identify languages, frameworks, and monorepo layout. This determines which tool matrix to apply in Phase 2. 3. **Check tooling availability.** Run `scripts/check-tools.sh`. Missing tools are reported as Phase 1 findings — continue with whichever tools are available rather than aborting. 4. **Load `.deadcode-ignore`.** If the target directory contains a `.deadcode-ignore` file, parse it and treat the patterns as suppression rules during Phase 7. 5. **Map project structure.** Inventory the codebase excluding `node_modules/`, `.venv/`, `venv/`, `target/`, `dist/`, `build/`, `.next/`, `.nuxt/`, `coverage/`, `.git/`. ## User Context $ARGUMENTS Detected stack: !`bash "${CLAUDE_PLUGIN_ROOT}/skills/dead-code-audit/scripts/detect-stack.sh" .`