What problem does it solve? Large, mixed-purpose diffs are hard to review: reviewers cannot tell what changed, why the slice exists, or whether it is safe. This Skill structures implementation plans, Invoker YAML workflows, and PR stacks so every diff makes exactly one locally reviewable claim with an explicit safety invariant. ## Core Features & Use Cases - Required slice metadata: Every slice carries a Review claim, Review lane (behavior, refactor, proof, cleanup, policy, or docs), Safety invariant, Slice rationale, Architectural effect, Alternatives, and Non-goals. - Ordering and boundary rules: Enforces evidence-before-change, refactor-before-behavior, foundation-before-exposure sequencing, and splits work across architectural boundaries such as migration, write path, API, and UI. - Refactoring discipline: Distinguishes decomposition/extraction refactors (one top-level symbol per PR) from rehome/relocation refactors (git-mv-shaped slices with forwarding shims), and requires naming the Fowler technique in every refactor-lane PR. - Use Case: Before authoring a multi-PR stack that splits a large module, use this Skill to sequence one extraction per slice, confirm each safety invariant with the user, and write PR bodies that state the claim instead of summarizing files. ## Quick Start Use the review-compression skill to split my planned changes into a PR stack where each diff has one review claim and a confirmed safety invariant.
