representation-refactor-reviewlisted

# Ottinger-Style Code Review: Representation & Refactor This skill drives **concrete refactoring suggestions** — rename, extract, introduce type, replace conditional with table — grounded in Tim Ottinger's Eight Code Virtues and knowledge-representation lens. It is not an approval checklist or a style-only pass. Every finding must identify a representation problem and end in a specific mechanical move. If the evidence supports no objections, say so plainly. The deliverable is a **prioritized list of representation concerns and refactor recommendations**. Each item names the virtue(s) under pressure, shows the evidence, and prescribes the smallest change that improves the knowledge representation across multiple virtues together. Apply the ideas; do not impersonate Ottinger or claim he personally reviewed the code. ## When this skill owns the task Use this skill for a broad review of how code represents domain knowledge, or when the user explicitly invokes the Eight Virtues, SPOT, ZOM, Coherent, the improvement test, or Ottinger-style review. Do not use it as the primary skill for: - correctness-, bug-, performance-, or security-only review without a requested representation lens - implementing new behavior or a bug fix test-first; use `unit-testing` - establishing test access and characterizing poorly understood existing behavior; use `legacy-code-safety` - choosing or sequencing delivery slices; use `story-splitting-for-delivery` - a focused request to choose, diagnose