What is speckit-git-commit?

A Git hook that automatically stages and commits changes after configured Spec Kit commands finish. Spec Kit is a workflow for turning feature ideas into written specifications and implementation plans.

Use it to configure automatic commits for events such as specifying, planning, or implementing a feature.

It removes the need to manually save each completed workflow step as a Git commit.

How cloudposse/atmos configures Claude Code

About the project

Atmos is an infrastructure runtime that coordinates tools such as Terraform, OpenTofu, Kubernetes, Helm, Packer, Ansible, and containers through consistent commands and configuration. It is for teams running cloud infrastructure on laptops, in CI, or through AI agents across environments and regions. Its catalogue entries provide skills, agents, commands, and other add-ons for Atmos workflows.

cloudposse/atmos · 1,403 stars · on GitHub · atmos.tools

Reuse

Borrowing it

Nothing to install: this file belongs to cloudposse/atmos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/cloudposse/atmos/main/.claude/skills/speckit-git-commit/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/cloudposse/atmos

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/skills/cloudposse/atmos/speckit-git-commit/github.svg)](https://agentmods.dev/skills/cloudposse/atmos/speckit-git-commit)

Your own site

<a href="https://agentmods.dev/skills/cloudposse/atmos/speckit-git-commit"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/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/skills/cloudposse/atmos/speckit-git-commit"><img src="https://agentmods.dev/badge/skills/cloudposse/atmos/speckit-git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 473 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.00018	$0.00473
Opus 5.5	$0.00007	$0.00189
Sonnet 5.5	$0.00004	$0.00095
Haiku 4.5	$0.00002	$0.00047

Measured 1mo ago against content hash 18ade7acd557, 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 1mo 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 — 1 line 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.

.claude/skills/speckit-git-commit/SKILL.md · 54 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.

1mo ago First seen · 54 lines · 18 tokens per session scan A 18ade7acd557

Subscribe to this mod's changes

speckit-git-commit is a skill published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 473 once invoked, about $0.0001 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 1 line, and is treated as a copy.

Cloud DevOps and cloud Git and workflow Orchestration Planning automation cli hcl2

csv

CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".

x-cmd/x-cmd · 49 tokens

git

Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".

x-cmd/x-cmd · 58 tokens

work

Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.

x-cmd/x-cmd · 29 tokens

gke-basics

Trigger: Use when working with Google Kubernetes Engine basics — cluster setup, node pools, workloads, networking, and storage fundamentals.

skillmds/skillmd · 4 tokens

repo

Convention + tooling for where agent-cloned repos live and how their worktrees are arranged. Default bare repo at /.x-repo/.bare/ / / .git with linked working trees under /.x-repo/ / / [/@ ]. Discovered via x repo ls. Worktree management via x repo wt. Use for "where to clone", "git clone path", "workspace layout"…

x-cmd/x-cmd · 110 tokens

gh

You have access to gh (GitHub CLI) for repository and project management.

agents-squads/squads-cli · 0 tokens

atmos: Skill for Claude Code