controlflow-reviewlisted

# ControlFlow Review ## Overview Review changes by prioritizing correctness, regression risk, and evidence over style. Use this for code or completed-phase review; use `/controlflow-claude-code:controlflow-plan-audit` or `/controlflow-claude-code:controlflow-assumption-verifier` for pre-execution plan review. Invoke this skill via `/controlflow-claude-code:controlflow-review`. ## Local Contract - Findings first, ordered by severity, with file/line evidence and confidence. - Distinguish validated blockers from hypotheses; state validation gaps explicitly. - Compare implementation to the plan when one exists; scope drift is a review issue. - Use [references/review-checklist.md](references/review-checklist.md), [references/validation-status.md](references/validation-status.md), and [../controlflow-planning/references/llm-behavior-guidelines.md](../controlflow-planning/references/llm-behavior-guidelines.md) for shared checklist and evidence discipline. ## Workflow 1. Check correctness, regressions, security, data integrity, performance, and contract drift before style. 2. Validate feasible suspicions with commands, file reads, or schema checks. 3. Label each finding with severity, confidence, file, line, and user impact. 4. Present findings first; if there are none, say so and name residual risks or test gaps. 5. Use structured text, not raw JSON. ## Review Axes Check correctness/functionality, security, architecture/design, maintainability/style, and test quali