Work-Unit Commit Planner
Plans git commits and PRs as small, reviewable units with tests and docs included
- Repository
- Gentleman-Programming/gentle-ai
- Stars
- 8,181
- Licence
- MIT
- Files
- 1 file
What it does
When installed, the agent plans how to split a change into commits and pull requests that each deliver one clear behavior, fix, or docs update. It keeps tests and docs in the same commit as the code they describe, avoids splitting work by file type (like all models first, then services, then tests), checks each commit against a short checklist, and writes Conventional Commit messages that explain the outcome. For large changes it suggests a chain of stacked PRs, each near about 400 changed lines.
Great for
- Developers preparing a feature branch for code review
- Teams that use stacked or chained pull requests
- Engineers who want cleaner commit history and easier rollbacks
Skip it if
- Solo projects that do not care about commit structure (the checklist adds overhead with little benefit)
- Repositories that require a different commit or PR convention, since the skill assumes Conventional Commits and a roughly 400-line review budget
Try asking
- “Split this feature into reviewable commits that each keep tests and docs with the code”
- “Plan a chained PR set for this large refactor, staying near 400 changed lines per PR”
- “Review my staged changes and suggest a commit message that explains the outcome”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
work-unit-commits.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip work-unit-commits.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip work-unit-commits.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Run git diff --stat and git diff --cached --stat first so the agent can see the real size of the change before planning.
- Tell the agent your review budget if your team uses a limit other than 400 lines.
- Ask the agent to show the planned commit list before it commits anything.
What's inside
- SKILL.md
Redistributed unmodified from Gentleman-Programming/gentle-ai under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.