committing-scoped-changes — Claude Code skill
committing-scoped-changes splits an explicit list of files or folders into separate git commits and leaves the rest of the working tree alone.
no license 153 installs ★ 3 updated 2026-10-25
npx skills add b-mendoza/agent-skills --skill committing-scoped-changes -a claude-codeWhat committing-scoped-changes does
You hand the skill a set of paths: exact files, or folders written with a trailing slash. Globs are rejected, spelling has to match the repository, and a rename counts only when both sides are listed.
It runs in two stages. A read-only subagent called commit-boundary-planner reads the state of the repo and writes a plan; you approve that plan in one go; then scoped-commit-executor commits one group at a time with git commit --only -- <paths>. Entries staged from elsewhere stay staged. The report format is checked by scripts/validate-output.sh.
Nothing gets committed until you ask for it in words in the current conversation. An unfinished merge, rebase, cherry-pick or bisect stops the run. Pushing and amending are not part of what it does.
What it helps with
- commit only the files under
src/payments/without disturbing what is already staged - split a pile of edits into separate atomic commits
- keep unrelated experiments out of a ticket commit
- verify that no stray file slipped into the commit
Example prompts for the agent
- Commit only the changes in
src/payments/andtests/payments.test.ts, leave the rest alone. - Split my working tree into atomic commits for
JNS-6880. - Make the commit for
src/checkoutin Conventional Commits style.
How to install committing-scoped-changes
1Skills CLI (Vercel)
npx skills add b-mendoza/agent-skills --skill committing-scoped-changes -a claude-code2Manually: put the files in place
~/.claude/skills/committing-scoped-changes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/committing-scoped-changes/
1Skills CLI (Vercel)
npx skills add b-mendoza/agent-skills --skill committing-scoped-changes -a codex2Manually: put the files in place
.agents/skills/committing-scoped-changes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add b-mendoza/agent-skills --skill committing-scoped-changes -a cursor2Manually: put the files in place
.cursor/skills/committing-scoped-changes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install b-mendoza/agent-skills skills/committing-scoped-changes2Manually: put the files in place
.github/skills/committing-scoped-changes/SKILL.md1Skills CLI (Vercel)
npx skills add b-mendoza/agent-skills --skill committing-scoped-changes -a gemini-cli2Platform CLI
gemini skills install https://github.com/b-mendoza/agent-skills --path skills/committing-scoped-changesManually: put the files in place
.devin/skills/committing-scoped-changes/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add b-mendoza/agent-skills --skill committing-scoped-changes -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about committing-scoped-changes
How do I install committing-scoped-changes in Claude Code?
Run npx skills add b-mendoza/agent-skills --skill committing-scoped-changes -a claude-code; the skill lands at ~/.claude/skills/committing-scoped-changes/SKILL.md.
What does committing-scoped-changes do?
It builds atomic git commits from a named set of files or folders and keeps work outside that set out of them.
Can I pass a whole folder or a wildcard?
A folder works when the path ends with /. Wildcards and globs are turned down, and the spelling must match the repository path.