What problem does it solve? Large changes often become monolithic commits or PRs that reviewers cannot reasonably evaluate, mixing unrelated files and leaving tests or docs detached from the behavior they verify. ## Core Features & Use Cases - Work-unit commit planning: Splits features into commits where each one represents a deliverable behavior, fix, migration, or docs unit that stands on its own. - Review workload guardrails: Applies a 400-changed-line threshold to decide when commits should be promoted into chained or stacked PRs, aligned with SDD delivery strategies. - Verification and rollback evidence: Requires each unit to record focused test results, runtime harness results (or an explicit N/A), and a rollback boundary that removes no unrelated work. - Use Case: When implementing a multi-part feature, use this Skill to split the work into Conventional Commits like feat(auth): add token validation domain model and tests, keeping tests and docs with each behavior. ## Quick Start Ask the assistant to split the current feature implementation into reviewable work-unit commits with tests, docs, and rollback boundaries recorded for each one.
