01-commit — Claude Code skill: commits and installation
The 01-commit skill stages changes one concern at a time, writes a conventional commit message, and commits locally. It can push the branch when asked.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-vcs@aidd-frameworkWhat 01-commit does
The workflow has three steps: collect files for one concern, write the commit message, then commit. Separate concerns become separate commits. For the message format, the skill checks aidd_docs/memory/vcs.md first and falls back to assets/commit-template.md when the project has no convention there.
After a hook rejects a commit, the skill retries only when the fix is deterministic and stays within the current commit’s files. It must not widen the change just to pass a check. Commits stay local unless the push option is set. Force-pushing is barred; --force-with-lease is allowed only on explicit request.
In auto mode, the skill does not ask questions. interactive mode asks for confirmation before staging and before each split. It does not handle amending, rebasing, pull requests, or release tags.
What it helps with
- split unrelated work into separate commits
- write a conventional message using project rules
- retry a rejected hook after a scoped fix
- push a branch when requested
Example prompts for the agent
- Create commits for the changes in
src/auth.tsusing the project’s conventions. - Split the current changes into commits by concern and use
interactivemode. - Commit the changes and push the branch.
How to install 01-commit
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-vcs@aidd-frameworkThis installs the whole aidd-vcs plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 01-commit -a claude-code3Manually: put the files in place
~/.claude/skills/01-commit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/01-commit/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 01-commit -a codex2Manually: put the files in place
.agents/skills/01-commit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 01-commit -a cursor2Manually: put the files in place
.cursor/skills/01-commit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-vcs/skills/01-commit2Manually: put the files in place
.github/skills/01-commit/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 01-commit -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-vcs/skills/01-commitManually: put the files in place
.devin/skills/01-commit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 01-commit -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 01-commit
How do I install 01-commit in Claude Code?
Add the marketplace with /plugin marketplace add ai-driven-dev/framework, then install the plugin with /plugin install aidd-vcs@aidd-framework.
What does 01-commit do?
It stages files for one concern, writes a conventional commit message, and creates the commit. It can also push the branch when asked.
When does 01-commit retry after a hook rejects a commit?
Only when the fix is deterministic and limited to files in the current commit. It will not widen the change to satisfy a check.
Source text
SKILL.md · MIT
--- name: 01-commit description: Create atomic conventional commits; safely retry scoped hook fixes; optionally push. Use when the user wants to commit changes, optionally pushing the branch. Not for amending, rebasing, opening a pull request, or tagging a release. argument-hint: paths | auto | push --- # Commit Stage, message, commit. `01 → 02 → 03`. ## Actions | # | Action | Step | | --- | --------- | ---------------------------------------------- | | 01 | `collect` | Stage one concern | | 02 | `message` | Write the conventional message | | 03 | `commit` | Commit, safely retry scoped fixes, push if asked | Several concerns means several commits: repeat the chain, one concern at a time. Before running an action, read its file in `actions/`, not only the table or assets. ## Transversal rules - Follow the project's convention in `aidd_docs/memory/vcs.md` when set, else `assets/commit-template.md`. - One concern per commit. Imperative mood. The body says why, not what. - Reference the issue in the body when there is one. - Never `--force` push; `--force-with-lease` only when explicitly asked. - Retry a rejected hook only for deterministic changes within the current commit's files. Never broaden the change to make a check pass. - `auto` never prompts. `interactive` confirms before staging and before each split. - Commits locally by default; pushes as well only when the push option is set. ## Assets - `assets/commit-template.md`: Conventional commit format reference.
© AI-Driven Dev · MIT · ai-driven-dev/framework