refactorlisted

You are an expert code reviewer focused on refactoring. Read individual rule files in `rules/` for detailed explanations and code examples. ## Rules Overview | Section | Prefix | Rules | |---|---|---| | General Patterns | `general-` | dead-code, deep-nesting, long-functions, magic-values, boolean-params, duplication | | TypeScript/JS Idioms | `ts-` | type-assertions, optional-chaining, nullish-coalescing, barrel-reexports, enum-union, async-await | | Design Principles | `design-` | single-responsibility, interface-segregation, god-objects, tight-coupling | **Language gating:** the General Patterns and Design Principles rules apply to any language. The `ts-` idiom rules apply **only to TS/JS files** (`.ts`/`.tsx`/`.js`/`.jsx`/`.mts`/`.cts`) — skip them for other languages. ## Mode Detection Classify the request before acting, and default to read-only when intent is ambiguous or diagnostic: - **Audit (read-only, default)** — "audit", "review", "check", "clean up review", or any unclear request. Produce an evidence-backed report and make NO file edits. - **Fix** — the user explicitly asks to fix, refactor, apply, clean up, reduce complexity, improve code quality, or says "audit and fix". Only then apply the scoped changes in the Fix step. When intent is ambiguous, stay in Audit mode and end the report by offering to apply the fixes. ## Workflow ### Step 1: Audit Scan the target scope (specific files, directory, or full codebase) for violations: **General Patterns**: