code-quality-auditlisted

# Code Quality Audit ## Core Rule Surface issues that affect maintainability and correctness, not stylistic preferences. Recommend fixes only with concrete reproduction steps; never apply edits in a report-only request. ## 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 `/code-quality-audit` when: - Reviewing a codebase for code smells before a refactoring sprint - Onboarding to a new project and assessing code health - Preparing for a code review or due diligence assessment - After rapid development to identify accumulated technical debt ## Default Behavior When the user asks to audit, scan, review, or "give me a report" for code quality, produce the full code-quality-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 i