work-unit-commits

by Gentleman-Programming7.8k

Developer Tools

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add Gentleman-Programming/gentle-ai --skill work-unit-commits -a cursor -y

How do I install work-unit-commits?: Download internal/assets/skills/work-unit-commits/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does work-unit-commits live?: The publisher keeps it at https://github.com/Gentleman-Programming/gentle-ai.
Which agents can use work-unit-commits?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

Load this skill when deciding what belongs in each commit or PR.

Use it for:

Commit by work unit	A commit represents a deliverable behavior, fix, migration, or docs unit.
Do not commit by file type	Avoid `models`, then `services`, then `tests` if none works alone.
Keep tests with code	Tests belong in the same commit as the behavior they verify.
Keep docs with the user-visible change	Docs belong with the feature or workflow they explain.
Tell a story	A reviewer should understand why each commit exists from its diff and message.
Future PR-ready	Each commit should be a candidate chained PR when the change grows.
Budget is not code-golf	Never shrink a diff by deleting comments, blank lines, docs, or tests, or by compressing code, to fit the review budget (400 by default, or the session `review_budget_lines`). Slice by work unit or report the overage.

Weak split	Better work-unit split
`add models`	`feat(auth): add token validation domain model and tests`
`add services`	`feat(auth): wire token validation into login flow`
`add tests`	Tests included with each behavior commit
`update docs`	Docs included with the user-facing change they explain