What is speckit.git.commit?

A Git hook that automatically stages and commits project changes after a Spec Kit command runs. Spec Kit is a tool for guiding software work through written specifications and plans.

It helps record changes after commands such as specifying, planning, or implementing. It can run through Bash or PowerShell and read its settings from a YAML file.

It removes the need to remember to save each command’s changes in Git. You can enable or disable commits for specific hook events and choose commit messages.

speckit.git.commit — Command by MartinKuhne

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/martinkuhne/devstack/speckit.git.commit

Clone the repo

git clone --depth 1 https://github.com/MartinKuhne/devstack

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 426 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.00426
Opus 5	$0.00005	$0.00213
Sonnet 5	$0.00002	$0.00085
Haiku 4.5	$0.00001	$0.00043

Measured yesterday against content hash 445ed4cd43c8, 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.

Origin

This is a copy

100% identical to speckit.git.commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.specify/extensions/git/commands/speckit.git.commit.md · 49 lines

What it actually says

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
Uses the per-command message if configured, otherwise a default message
If enabled and there are uncommitted changes, runs git add . + git commit

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>
PowerShell: .specify/extensions/git/scripts/powershell/auto-commit.ps1 <event_name>

Replace <event_name> with the actual hook event (e.g., after_specify, before_plan, after_implement).

Configuration

In .specify/extensions/git/git-config.yml:

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

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 · 49 lines · 10 tokens per session scan A 445ed4cd43c8

Subscribe to this mod's changes

speckit.git.commit is a command published in the GitHub repository MartinKuhne/devstack (2 stars, last pushed 20d ago), licensed MIT. It adds 10 tokens to every session and 426 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.git.commit, differing in 0 lines, and is treated as a copy.

Git and workflow Planning

speckit.git.commit

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

Auto-Commit Changes

Behavior

Execution

Configuration

Graceful Degradation

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement