simplifylisted

Simplify recently changed material while preserving what it does. Prioritize readable, explicit results over compact ones — fewer lines is not the goal. The contract below governs every step of this pass, and travels verbatim to each fixer dispatched in Step 2. <preservation-contract> Preserve what the material does. Which test that is depends on the material, and a file is judged by its own kind — a diff holding both kinds is held to both: - **Code** — same output for every input, same error behavior, same side effects and ordering. - **Agent-facing prose** (a skill, an `AGENTS.md` or `CLAUDE.md`, a rules file — anything an agent loads and acts on) — the instruction set is what is preserved. Cut text that repeats, rambles, or restates what another file already says. Never cut or weaken a sentence that directs an agent to act, forbids an action, gates a step behind a condition, or states how completion is judged — rewording one into a suggestion is weakening it. Where a sentence's kind is uncertain, it stays. </preservation-contract> ## Step 1: Resolve the scope 1. **If the user named a scope** (a file, a directory, "the function I just wrote"), use it as authoritative — do not widen it. 2. **Otherwise**, use the diff between the current branch and its merge-base with the default branch (`git diff <default-branch>...`) plus the uncommitted changes (`git diff HEAD`), which a merge-base diff leaves out. With no base ref, the uncommitted changes alone. Either wa