commit
Use when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current branch, or recovering after raw Git commands. Load and follow the git-spice skill for the workflow.
Best use case
commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current branch, or recovering after raw Git commands. Load and follow the git-spice skill for the workflow.
Teams using commit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/commit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How commit Compares
| Feature / Agent | commit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current branch, or recovering after raw Git commands. Load and follow the git-spice skill for the workflow.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Commit Command Use the `git-spice` skill to commit, amend, fix up, branch, or stack work exactly as described there. For any commit, branch-as-part-of-commit, stacking, or raw-Git-recovery task, first load and follow: ```text ~/.agents/skills/git-spice/SKILL.md ``` That skill is the authoritative manual for: - Creating commits - Amending commits - Creating fixup commits - Creating or stacking branches - Inserting work below the current branch - Recovering from raw Git usage - Applying the commit message reference For commit message writing, the canonical reference is: ```text ~/.agents/skills/git-spice/references/writing-commit-messages.md ``` Do not invent a separate commit workflow here. Load `git-spice`, then perform the commit operation exactly as that skill describes.