melech-diff-minimizer

# Diff Minimizer Take an implementation that already exists and make it smaller, more local, and safer to review without weakening what it must accomplish. ## Goal > Preserve the PR's required behavior with the smallest safe diff and semantic > blast radius. Do not optimize line count blindly. A three-line change in shared infrastructure can be riskier than thirty isolated lines in a leaf module. Optimize in this order: 1. Preserve required behavior, compatibility, and correctness. 2. Avoid touching shared systems, public contracts, schemas, persisted data, dependencies, and cross-cutting state. 3. Reduce affected subsystems, files, call sites, concepts, and code paths. 4. Reduce changed lines. Local duplication is acceptable when a shared abstraction would expose more of the system to regression. ## Boundary With Other Skills - **`melech-8020`** may negotiate or narrow the outcome to find a cheaper useful path before implementation. - **`melech-prune`** proves and removes dead code, zombie paths, and YAGNI residue. - **`melech-diff-minimizer`** keeps the outcome fixed and may replace a working, necessary implementation with a narrower one. If the only meaningful reduction requires dropping or changing behavior, stop and hand that product trade-off to the user or `melech-8020`. Do not call a weaker result equivalent. ## Workflow ### 1. Establish the contract and diff Resolve the comparison target from the user's command, PR metadata, or repository conventi...