What is speckit.git.commit?

An automatic Git commit command that stages and commits project changes after or before configured workflow commands. A commit is a saved set of changes in Git.

Use it as a workflow hook to commit changed files automatically, with fixed or Conventional Commit-style messages.

It saves command-generated changes according to configured events and commit-message rules instead of leaving them uncommitted.

speckit.git.commit — Command for Claude Code by loulanyue/spec-kit-zh

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.

Clone the repo

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

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/speckit.git.commit/github.svg)](https://agentmods.dev/commands/loulanyue/spec-kit-zh/speckit.git.commit)

Your own site

<a href="https://agentmods.dev/commands/loulanyue/spec-kit-zh/speckit.git.commit"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/speckit.git.commit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/loulanyue/spec-kit-zh/speckit.git.commit"><img src="https://agentmods.dev/badge/commands/loulanyue/spec-kit-zh/speckit.git.commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00010	$0.00858
Opus 5.5	$0.00004	$0.00343
Sonnet 5.5	$0.00002	$0.00172
Haiku 4.5	$0.00001	$0.00086

Measured 14d ago against content hash 8e6826f16136, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 14d ago.

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.

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.

14d ago 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 loulanyue/spec-kit-zh (337 stars, last pushed 13d ago), licensed MIT. It adds 10 tokens to every session and 858 once invoked, about $0.0000 per session on Opus 5.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.

Claude Code Commits Git and workflow ai-coding chinese codex cursor developer-tools

branch-commit

Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…

Mozurok/fhorja.dev · 111 tokens

approve-proposed

Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block, promoting staged content to real files. Invoked on request only. Use when that block contained files marked PROPOSED and you have accepted the inline content of each. Do not use when the prior turn had…

Mozurok/fhorja.dev · 107 tokens

pr-package

Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…

Mozurok/fhorja.dev · 109 tokens

speckit.git.commit