gentle-ai-work-unit-commits

1## When to Use
2 
3Load this skill when deciding what belongs in each commit or PR.
4 
5Use it for:
6 
7- Splitting a feature into reviewable work.
8- Preparing commits before opening a PR.
9- Turning a large change into chained or stacked PRs.
10- Keeping reviewer cognitive load healthy.
11- Committing ODD work in reviewable slices of about 400 authored changed lines.
12 
13## Critical Rules
14 
15| Rule | Requirement |
16|------|-------------|
17| Commit by work unit | A commit represents a deliverable behavior, fix, migration, or docs unit. |
18| Do not commit by file type | Avoid `models`, then `services`, then `tests` if none works alone. |
19| Keep tests with code | Tests belong in the same commit as the behavior they verify. |
20| Keep docs with the user-visible change | Docs belong with the feature or workflow they explain. |
21| Tell a story | A reviewer should understand why each commit exists from its diff and message. |
22| Future PR-ready | Each commit should be a candidate chained PR when the change grows. |
23| Delivery workload guard | If the task forecast produces a >400-line change, honor the selected `delivery_strategy`. On chaining paths only, group commits into chained PR slices before implementation. For explicit `single-pr` or `exception-ok`, keep one PR, report the review load, and follow the destination repository's documented contribution/size policy; selection alone does not accept an exception. |
24…