testing-auditlisted

# Testing Audit ## Core Rule Distinguish test gaps from test churn. Report missing critical-path coverage and flaky tests separately; never recommend tests beyond reproducibility need. ## 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 `/testing-audit` when: - Test suite is unreliable or has frequent flaky tests - Coverage numbers look good but bugs still slip through - Planning a testing strategy improvement - Reviewing test quality after rapid feature development - Assessing confidence level before a major release ## Default Behavior When the user asks to audit, scan, review, or "give me a report" for test coverage and quality, produce the full testing-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 found dur