speckit-git-commit

Automatically stage and commit changes after Spec Kit commands complete.

Updated May 22, 2026
One-click install
npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-git-commit-wu-mao-chia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/WU-MAO-CHIA/AI_tset_platfrom/tree/main/.opencode/skills/speckit-git-commit
Command: npx skills add https://github.com/WU-MAO-CHIA/AI_tset_platfrom --skill speckit-git-commit-wu-mao-chia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running Spec Kit commands like specify, plan, or implement, generated artifacts often sit uncommitted in the working tree, risking lost work and messy history. This Skill automates the commit step so every Spec Kit event produces a clean, traceable Git commit. ## Core Features & Use Cases - Hook-Based Auto-Commit: Runs as a before/after hook on Spec Kit commands, detecting the event name (e.g., after_specify, before_plan) from the hook context. - Configurable Per-Event Behavior: Reads .specify/extensions/git/git-config.yml to enable or disable auto-commit per event, with custom commit messages and a global default toggle. - Graceful Degradation: Skips safely when Git is unavailable, the directory is not a repository, no config exists, or there are no changes to commit. - Use Case: A team using Spec Kit for spec-driven development enables after_specify auto-commit so every generated specification is immediately versioned with the message "[Spec Kit] Add specification". ## Quick Start Enable auto-commit in .specify/extensions/git/git-config.yml and ask the assistant to run the auto-commit script for the current Spec Kit hook event.

Frequently Asked Questions about speckit-git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-commit changes after Spec Kit commands?▼

Enable auto_commit in .specify/extensions/git/git-config.yml by setting default to true or enabling specific events like after_specify. The hook then runs the auto-commit script, which stages all changes and commits with the configured message.

How do I configure commit messages for Spec Kit hooks?▼

Add a message field under each event key in the auto_commit section of git-config.yml, for example message: "[Spec Kit] Add specification" under after_specify. If no per-command message is set, a default message is used.

Does the auto-commit hook work on Windows PowerShell?▼

Yes, the Skill provides both Bash and PowerShell scripts. Run .specify/extensions/git/scripts/powershell/auto-commit.ps1 with the event name on Windows, or the Bash equivalent on Unix systems.

What happens if auto-commit runs outside a Git repository?▼

The hook degrades gracefully and skips with a warning. It also skips when no config file exists, when auto-commit is disabled for the event, or when there are no uncommitted changes.

Can I enable auto-commit for only some Spec Kit commands?▼

Yes, each event has its own enabled flag that overrides the global default. For example, you can enable after_specify while keeping after_plan disabled in the same configuration file.