commit · fradser — Claude Code skill: what it does, how to install
This skill creates atomic conventional commits through git-agent. Use it when a short intent should become a focused Git commit.
MIT 121 installs ★ 597 updated 2026-11-06
npx skills add FradSer/dotclaude --skill commit -a claude-codeWhat commit does
The skill derives a one-sentence intent from the request or supplied arguments, then runs git-agent commit --intent "<intent>". When the relevant files are already staged, it adds --no-stage; after a 401 authentication error, it retries with --free. An exact conventional commit subject can be passed as the --intent value.
It calls git-agent commit without first running git status, git diff, or git log. Starting with v0.7.0, git-agent detects model attribution from session environment variables. The binary must be available: if git-agent cannot be found, the commit is not created and the user is asked to install it or run Git commands manually.
What it helps with
- create an atomic conventional commit
- commit files that are already staged
- retry a commit after a 401 authentication error
- set an exact commit subject from the intent
- attach a co-author to the commit
Example prompts for the agent
- Create a commit for fixing API error handling.
- Commit the files already staged without changing their staging state.
- Create the commit with co-author
Alexusing--co-author.
How to install commit
1Skills CLI (Vercel)
npx skills add FradSer/dotclaude --skill commit -a claude-code2Manually: put the files in place
~/.claude/skills/commit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/commit/
1Skills CLI (Vercel)
npx skills add FradSer/dotclaude --skill commit -a codex2Manually: put the files in place
.agents/skills/commit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add FradSer/dotclaude --skill commit -a cursor2Manually: put the files in place
.cursor/skills/commit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install FradSer/dotclaude git-agent/skills/commit2Manually: put the files in place
.github/skills/commit/SKILL.md1Skills CLI (Vercel)
npx skills add FradSer/dotclaude --skill commit -a gemini-cli2Platform CLI
gemini skills install https://github.com/FradSer/dotclaude --path git-agent/skills/commitManually: put the files in place
.devin/skills/commit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add FradSer/dotclaude --skill 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 commit
How do I install commit in Claude Code?
Run npx skills add FradSer/dotclaude --skill commit -a claude-code. The skill file will be placed at ~/.claude/skills/commit/SKILL.md.
What does commit do?
It creates an atomic conventional Git commit through git-agent, using an intent derived from the request or arguments. It adds --no-stage when the files are already staged.
What happens after a 401 authentication error?
The skill retries the command with --free. If the git-agent binary is missing, it reports the error and asks the user to install git-agent or run Git commands manually.
Source text
SKILL.md · MIT
--- name: commit description: Creates atomic conventional git commits using git-agent. This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit changes using AI atomic commits. user-invocable: true argument-hint: "[intent or --co-author]" allowed-tools: ["Bash(git-agent:*)", "Bash(git:*)"] --- CRITICAL: - Do NOT run `git status`, `git diff`, `git log`, or any other read commands before `git-agent commit`. - Execute `git-agent commit` directly. `git-agent` (v0.7.0+) automatically detects active model attribution from session environment variables (`PI_MODEL`, etc.). ## Execution 1. Derive a concise one-sentence intent from the conversation or `$ARGUMENTS`. 2. Pass `--co-author "<co-author>"` if explicitly specified in `$ARGUMENTS` or user instructions. 3. Run primary commit command: ```bash git-agent commit --intent "<intent>" ``` 4. If specific files are already staged, pass `--no-stage`: ```bash git-agent commit --no-stage --intent "<intent>" ``` 5. On auth error (401), retry with `--free`: ```bash git-agent commit --free --intent "<intent>" ``` 6. **Fallback** (if `git-agent` binary is not found): report the error and ask the user to install git-agent or run git commands manually. CLI Reference: `../../references/cli.md` Attribution & retry-ladder reference: `../../references/coauthor-attribution.md` (covers `--no-attribution` and the `--free` retry) > **Deterministic messages:** When an exact commit message is required (e.g. version bump `chore: bump version to 0.11.0`), pass the full conventional message as the `--intent` value. The intent is used as the commit subject verbatim.
© FradSer · MIT · FradSer/dotclaude
Similar skills
All skills for Git and GitHub →commit by other authors comes first.