Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Agent skill
Gentle AI Work Unit Commits
by Gentleman-Programming in Gentleman-Programming/gentle-shell
Plan commits as reviewable work units. An agent skill from Gentleman-Programming/gentle-shell.
Install Gentle AI Work Unit Commits
$ npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Gentleman-Programming/gentle-shell gentle-ai-work-unit-commits --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Gentleman-Programming/gentle-shell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/work-unit-commits .claude/skills/gentle-ai-work-unit-commits && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gentle-ai-work-unit-commits" agent skill from https://github.com/Gentleman-Programming/gentle-shell/tree/main/skills/work-unit-commits into .claude/skills/gentle-ai-work-unit-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gentle-ai-work-unit-commits", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Gentleman-Programming/gentle-shell/tree/main/skills/work-unit-commitsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Gentleman-Programming/gentle-shell gentle-ai-work-unit-commits --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gentleman-Programming/gentle-shell.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/work-unit-commits .agents/skills/gentle-ai-work-unit-commits && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gentle-ai-work-unit-commits" agent skill from https://github.com/Gentleman-Programming/gentle-shell/tree/main/skills/work-unit-commits into .agents/skills/gentle-ai-work-unit-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gentle-ai-work-unit-commits", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Gentleman-Programming/gentle-shell gentle-ai-work-unit-commits --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gentleman-Programming/gentle-shell.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/work-unit-commits .cursor/skills/gentle-ai-work-unit-commits && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gentle-ai-work-unit-commits" agent skill from https://github.com/Gentleman-Programming/gentle-shell/tree/main/skills/work-unit-commits into .cursor/skills/gentle-ai-work-unit-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gentle-ai-work-unit-commits", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Gentleman-Programming/gentle-shell.git --path skills/work-unit-commits--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Gentleman-Programming/gentle-shell gentle-ai-work-unit-commits --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gentleman-Programming/gentle-shell.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/work-unit-commits .gemini/skills/gentle-ai-work-unit-commits && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gentle-ai-work-unit-commits" agent skill from https://github.com/Gentleman-Programming/gentle-shell/tree/main/skills/work-unit-commits into .gemini/skills/gentle-ai-work-unit-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gentle-ai-work-unit-commits", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Gentleman-Programming/gentle-shell gentle-ai-work-unit-commitsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Gentleman-Programming/gentle-shell.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/work-unit-commits .github/skills/gentle-ai-work-unit-commits && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gentle-ai-work-unit-commits" agent skill from https://github.com/Gentleman-Programming/gentle-shell/tree/main/skills/work-unit-commits into .github/skills/gentle-ai-work-unit-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gentle-ai-work-unit-commits", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Gentleman-Programming/gentle-shell gentle-ai-work-unit-commits --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gentleman-Programming/gentle-shell.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/work-unit-commits .opencode/skills/gentle-ai-work-unit-commits && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gentle-ai-work-unit-commits" agent skill from https://github.com/Gentleman-Programming/gentle-shell/tree/main/skills/work-unit-commits into .opencode/skills/gentle-ai-work-unit-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gentle-ai-work-unit-commits", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gentle-ai-work-unit-commits- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 646 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Plan commits as reviewable work units. An agent skill from Gentleman-Programming/gentle-shell.
- Works in 4 steps: Build the smallest independent work unit. → Include verification for that unit. → Commit it with a Conventional Commit… → …
- Development work in your project
- SKILL.md covers When to Use, Critical Rules, Work Unit Checklist and Split Examples, plus 4 more sections
- Calls git
What it does
Gentle AI Work Unit Commits is an agent skill from Gentleman-Programming/gentle-shell. Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Gentle Shell is a Pi-native coding-agent harness for controlled development with Organic Driven Development, optional SDD/OpenSpec, subagents, TDD evidence, review guardrails… The licence is Apache-2.0.
When your agent uses it
- Development work in your project
Example prompts
- “/gentle-ai-work-unit-commits”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Build the smallest independent work unit.
- Include verification for that unit.
- Commit it with a Conventional Commit message.
- If the PR approaches 400 changed lines, promote commits or groups of commits into chained PRs.
What it can do on your machine
Read from SKILL.md and the folder at commit 42653f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gentle AI Work Unit Commits loads about 1.2k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Gentleman-Programming/gentle-shell at commit 42653f7, republished under its Apache-2.0 licence (© Gentleman-Programming). 646 words, ~1,227 tokens.
Download SKILL.mdSave it as
.claude/skills/gentle-ai-work-unit-commits/SKILL.md (or your agent's skills folder).- name
- gentle-ai-work-unit-commits
- description
- Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
- license
- Apache-2.0
- metadata.author
- gentleman-programming
- metadata.version
- 1.0
When to Use
Load this skill when deciding what belongs in each commit or PR.
Use it for:
- Splitting a feature into reviewable work.
- Preparing commits before opening a PR.
- Turning a large change into chained or stacked PRs.
- Keeping reviewer cognitive load healthy.
- Applying SDD tasks without accidentally producing a PR above 400 changed lines.
- Closing an ODD task with a work-unit commit.
Critical Rules
| Rule | Requirement |
|---|---|
| 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. |
| SDD workload guard | If SDD tasks forecast 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. |
| 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. |
Work Unit Checklist
Before committing, confirm:
- The commit has one clear purpose.
- The repo still makes sense after applying only this commit.
- Tests or docs for this unit are included when relevant.
- Rollback is reasonable without reverting unrelated work.
- The commit message explains the outcome, not the file list.
Split Examples
| 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 |
PR Relationship
Use work-unit commits as the foundation for chained PRs:
- Build the smallest independent work unit.
- Include verification for that unit.
- Commit it with a Conventional Commit message.
- If the PR approaches 400 changed lines, promote commits or groups of commits into chained PRs.
Show full SKILL.md (252 more words)Show less
SDD Relationship
When sdd-tasks produces a Review Workload Forecast:
- Low risk: keep work-unit commits inside one PR.
- Medium risk: commit by work unit and monitor changed lines before PR creation.
- High risk: follow SDD
delivery_strategy— ask onask-on-risk, auto-slice with the cached chain choice onauto-chain, follow the destination repository's documented contribution/size policy on over-budgetsingle-pr, or record an explicitly accepted policy exception onexception-ok. A single-PR selection does not itself accept an exception. size:exceptionis a Gentle-owned repository policy, not a universal label requirement. Never request, create, or add the label for generic users unless the destination policy uses it; preserve its maintainer acceptance and protected-label authorization gates.- Splitting is bounded: after one honest slicing pass, if no cohesive work-unit split fits the budget, stop and report the smallest honest count and rationale. Recommend an exception only where destination policy provides it. Do not iterate shrinking the code to reach the number.
Each SDD work unit should map cleanly to a commit or PR with:
- clear start state,
- clear finished state,
- verification in the same unit,
- rollback that does not remove unrelated work.
ODD Relationship
Every ODD task closes with at least one work-unit commit:
- The native review candidate is that commit, or the PR slice it belongs to when review is deferred, evaluated against the previous reviewed boundary.
- The running authored line count from work-unit commits feeds the same delivery-strategy vocabulary as SDD.
- The feature document records the commit identity and, once a delivery strategy applies, the slice boundaries.
Commands
# Review the story before committing
git diff --stat
git diff --cached --stat
# Check recent commit style
git log --oneline -5© Gentleman-Programming, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/work-unit-commits of Gentleman-Programming/gentle-shell.
Open the folder on GitHubat commit 42653f7
Compare with similar skills
Gentle AI Work Unit Commits next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gentle AI Work Unit Commits this skillGentleman-Programming/gentle-shell | 1.2k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from Gentleman-Programming/gentle-shell
All 12 skills in this repoGentle AI Issue Creation
Gentleman-Programming/gentle-shell
Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.
Gentle AI Judgment Day
Gentleman-Programming/gentle-shell
Trigger: judgment day, judgement day, dual review, adversarial review, juzgar.
Gentle AI Branch and PR
Gentleman-Programming/gentle-shell
Prepares branches and pull requests for the Gentle AI repository, checking for a linked approved issue, labels, size budget and required checks.
Gentle AI Cognitive Doc Design
Gentleman-Programming/gentle-shell
Design docs that reduce cognitive load. An agent skill from Gentleman-Programming/gentle-shell.
Gentle AI Comment Writer
Gentleman-Programming/gentle-shell
Write warm, direct collaboration comments. An agent skill from Gentleman-Programming/gentle-shell.
Gentle AI Skill Creator
Gentleman-Programming/gentle-shell
Trigger: /skill-creation, skill creation, skill creator, create skill, new skill.
Related
Categories
Questions about Gentle AI Work Unit Commits
What does Gentle AI Work Unit Commits do?
Plan commits as reviewable work units. An agent skill from Gentleman-Programming/gentle-shell. Gentle AI Work Unit Commits is an agent skill from Gentleman-Programming/gentle-shell. Plan commits as reviewable work units.
When should I use Gentle AI Work Unit Commits?
Gentle AI Work Unit Commits fits situations like: development work in your project.
How do I install Gentle AI Work Unit Commits in Claude Code?
Run `npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a claude-code`. Or copy the skill folder (skills/work-unit-commits in Gentleman-Programming/gentle-shell) into .claude/skills/gentle-ai-work-unit-commits in your project. Claude Code loads it when a task matches its description.
How do I install Gentle AI Work Unit Commits in Codex?
Run `npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a codex`. Or copy the skill folder (skills/work-unit-commits in Gentleman-Programming/gentle-shell) into .agents/skills/gentle-ai-work-unit-commits in your project. Codex loads it when a task matches its description.
Can I use Gentle AI Work Unit Commits in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Gentleman-Programming/gentle-shell --skill gentle-ai-work-unit-commits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gentle-ai-work-unit-commits, .gemini/skills/gentle-ai-work-unit-commits, .github/skills/gentle-ai-work-unit-commits and .opencode/skills/gentle-ai-work-unit-commits in your project.
What does Gentle AI Work Unit Commits need to run?
Going by SKILL.md and its folder, Gentle AI Work Unit Commits needs the command-line tools its instructions call (git).
Does Gentle AI Work Unit Commits access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Gentle AI Work Unit Commits safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gentle AI Work Unit Commits use?
Gentle AI Work Unit Commits is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gentle AI Work Unit Commits use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gentle AI Work Unit Commits?
Skills that share tags, products or a category with Gentle AI Work Unit Commits: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gentle AI Work Unit Commits?
Gentleman-Programming (a GitHub organization) maintains it in Gentleman-Programming/gentle-shell, which has 1,245 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: Gentleman-Programming/gentle-shell on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.