speckit-git-commit

Automatically stages and commits changes after Spec Kit commands complete.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-git-commit-alkampfergit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/alkampfergit/cisharpai/tree/main/.claude/skills/speckit-git-commit
Command: npx skills add https://github.com/alkampfergit/cisharpai --skill speckit-git-commit-alkampfergit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running Spec Kit workflow commands like specify, plan, or implement, developers often forget to commit the generated artifacts, leaving specification work untracked in version control. This Skill automates that step by hooking into Spec Kit command lifecycle events and committing changes based on configurable rules. ## Core Features & Use Cases - Hook-Based Auto-Commit: Runs as a before/after hook on Spec Kit commands (e.g., after_specify, before_plan) and commits uncommitted changes when enabled. - Per-Event Configuration: Reads .specify/extensions/git/git-config.yml to enable or disable auto-commit per event with custom commit messages, falling back to a global default. - Graceful Degradation: Skips safely when Git is unavailable, the directory is not a repository, no config file 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 recorded in Git history with the message "[Spec Kit] Add specification". ## Quick Start Enable auto-commit in .specify/extensions/git/git-config.yml by setting auto_commit.default to true, then run any Spec Kit command and the changes will be committed automatically.

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 by creating .specify/extensions/git/git-config.yml with an auto_commit section. Set default to true for all commands, or enable specific events like after_specify with a custom message. The hook script then runs git add and git commit automatically.

How do I configure different commit messages per Spec Kit command?▼

Add per-event keys under auto_commit in git-config.yml, each with an enabled flag and a message field. For example, after_specify can use "[Spec Kit] Add specification" while after_plan uses a different message. Events without a key fall back to the default setting.

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

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 Linux and macOS.

What happens if Git is not installed or the folder is not a repository?▼

The skill degrades gracefully and skips with a warning instead of failing. 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 disable auto-commit for one specific Spec Kit command?▼

Yes, set the specific event key's enabled flag to false in git-config.yml, such as after_plan with enabled: false. Event-specific settings override the global auto_commit.default value.