speckit.git.commit — Claude Code command: what it does
speckit.git.commit is a Claude Code command that stages and commits changes after Spec Kit commands, according to project configuration.
MIT ★ 110 updated 2026-10-19
.claude/commands/speckit.git.commit.mdWhat speckit.git.commit does
The command acts as a lifecycle hook before or after core Spec Kit operations like after_specify and before_plan. It inspects .specify/extensions/git/git-config.yml to see whether auto-commit is enabled globally or for the triggering event. When pending changes exist, it triggers the companion Bash or PowerShell script.
Commit messages follow the chosen commit_style. With fixed, the script applies the predefined message string from the YAML file. In conventional mode, the agent inspects git diff output, constructs a single Conventional Commit headline, writes that headline to a temporary file, and passes the path to the script to prevent shell interpolation risks.
The command terminates without error if the directory lacks a Git repository or uncommitted work. If commit_style: conventional is configured but no generated message file is provided, the script halts with an explicit error.
What it helps with
- stage and commit modified files right after a Spec Kit step runs
- generate Conventional Commit summaries from pending repository diffs
- enable or mute automatic commits across specific lifecycle hooks
- pass generated commit text safely through temporary files avoiding shell execution
Example prompts for the agent
- Run the
after_specifyhook and commit generated specification changes - Inspect the diff for
after_planand create a conventional commit - Invoke
speckit.git.commitfor theafter_implementevent
How to install speckit.git.commit
Manually: put the files in place
.claude/commands/speckit.git.commit.mdCall it with /speckit.git.commit. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/speckit.git.commit.mdCall it with /prompts:speckit.git.commit. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/speckit.git.commit.prompt.mdManually: put the files in place
.gemini/commands/speckit.git.commit.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about speckit.git.commit
How to install speckit.git.commit in Claude Code?
Save the command specification directly to .claude/commands/speckit.git.commit.md.
What does speckit.git.commit do?
It reads .specify/extensions/git/git-config.yml and performs git add . followed by git commit whenever active hooks trigger on uncommitted edits.
What happens if no changes exist when the hook runs?
The script detects the clean working directory and exits cleanly with a warning message.
Source text
speckit.git.commit.md · MIT
---
description: "Auto-commit changes after a Spec Kit command completes"
---
# Auto-Commit Changes
Automatically stage and commit all changes after a Spec Kit command completes.
## Behavior
This command is invoked as a hook after (or before) core commands. It:
1. Determines the event name from the hook context (e.g., if invoked as an `after_specify` hook, the event is `after_specify`; if `before_plan`, the event is `before_plan`)
2. Checks `.specify/extensions/git/git-config.yml` for the `auto_commit` section
3. Looks up the specific event key to see if auto-commit is enabled
4. Falls back to `auto_commit.default` if no event-specific key exists
5. Determines the commit message based on `commit_style` (see below)
6. If enabled and there are uncommitted changes, runs `git add .` + `git commit`
## Commit Message Styles
Controlled by the `commit_style` key in `.specify/extensions/git/git-config.yml`:
- **`fixed`** (default): use the per-command `message` if configured, otherwise a generic `[Spec Kit] Auto-commit <phase> <command>` message.
- **`conventional`**: inspect the actual changes (`git diff` / `git status`) since the last commit and generate a single-line [Conventional Commit](https://www.conventionalcommits.org/) message (`type(scope): subject`, e.g. `feat: add OAuth specification` or `docs: update implementation plan`) that accurately summarizes the change. Write this message to a temporary file and pass the file's path to the script (see Execution below). The configured `message` values are ignored in this mode.
## Execution
Determine the event name from the hook that triggered this command, then run the script:
- **Bash**: `.specify/extensions/git/scripts/bash/auto-commit.sh <event_name> [--message-file <path>]`
- **PowerShell**: `.specify/extensions/git/scripts/powershell/auto-commit.ps1 <event_name> [-MessageFile <path>]`
Replace `<event_name>` with the actual hook event (e.g., `after_specify`, `before_plan`, `after_implement`). Only pass a generated message when `commit_style: conventional` is configured — first check `.specify/extensions/git/git-config.yml` for the value of `commit_style`:
- If `conventional`: inspect the diff and generate a Conventional Commit message. **Do not interpolate the generated message directly into a shell command string** — its content is derived from repository changes and may contain characters (quotes, `$(...)`, backticks) that a shell would execute or that would break command quoting. Instead, write the message to a temporary file using your file-editing tool (not a shell `echo`/`printf`), then pass that file's path via `--message-file <path>` (Bash) or `-MessageFile <path>` (PowerShell).
- If `fixed` or absent: run the script with just `<event_name>`; it uses the configured/static message.
## Configuration
In `.specify/extensions/git/git-config.yml`:
```yaml
# "fixed" (default) uses the messages below; "conventional" asks the agent
# to generate a Conventional Commit message from the diff instead.
commit_style: fixed
auto_commit:
default: false # Global toggle — set true to enable for all commands
after_specify:
enabled: true # Override per-command
message: "[Spec Kit] Add specification"
after_plan:
enabled: false
message: "[Spec Kit] Add implementation plan"
```
## Graceful Degradation
- If Git is not available or the current directory is not a repository: skips with a warning
- If no config file exists: skips (disabled by default)
- If no changes to commit: skips with a message
- If `commit_style: conventional` is set and no generated message was supplied: fails with a clear error instead of silently falling back to the fixed message format
© alfredoperez · MIT · alfredoperez/speckit-companion