What is speckit.git.commit?

A Git automation command that stages and commits project changes after a Spec Kit command runs. Git is a version-control system that records changes to code.

Use it as a hook for automatic commits, with configurable events and either fixed or Conventional Commit messages.

It removes the need to remember to create a commit after each configured workflow step.

speckit.git.commit — Command by github

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/github/spec-kit/speckit.git.commit

Clone the repo

git clone --depth 1 https://github.com/github/spec-kit

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 858 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00010	$0.00858
Opus 5	$0.00005	$0.00429
Sonnet 5	$0.00002	$0.00172
Haiku 4.5	$0.00001	$0.00086

Measured yesterday against content hash 8e6826f16136, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

speckit.git.commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

extensions/git/commands/speckit.git.commit.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

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)
Checks .specify/extensions/git/git-config.yml for the auto_commit section
Looks up the specific event key to see if auto-commit is enabled
Falls back to auto_commit.default if no event-specific key exists
Determines the commit message based on commit_style (see below)
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 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:

Read the full file on GitHub · 64 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 64 lines · 10 tokens per session scan A 8e6826f16136

Subscribe to this mod's changes

speckit.git.commit is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 858 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Planning Productivity ai copilot development engineering prd spec

speckit.git.commit

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Auto-Commit Changes

Behavior

Commit Message Styles

Execution

What this file has done since we first saw it

Other commands, from other repositories

book-internalize

book-style

stardust-session

book-characters

book-formula

stardust-list