What problem does it solve? Large changes often get committed by file type (models, then services, then tests), producing commits that do not work alone and PRs that are too big to review. This Skill guides you to split work into self-contained commits that tell a story and stay under reviewable size limits. ## Core Features & Use Cases - Work Unit Commit Rules: Each commit represents one deliverable behavior, fix, migration, or docs unit, with tests and docs kept alongside the code they verify. - Chained PR Planning: When a change approaches 400 changed lines, commits are grouped into chained or stacked PR slices following SDD delivery strategies. - Verification Checklist: Every unit records a focused test command with exact result, a runtime harness scenario or explicit N/A, and a rollback boundary naming removable files. - Use Case: While implementing a multi-task feature, use this Skill to decide what belongs in each commit so a reviewer understands why each change exists and any single commit can be rolled back without touching unrelated work. ## Quick Start Ask the assistant to split the current uncommitted changes into reviewable work-unit commits with tests included and a rollback boundary for each.
