speckit-git-commit

Automates git commits after Spec Kit hook events using per-event config.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/arosenkranz/kranz-tv --skill speckit-git-commit-arosenkranz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/arosenkranz/kranz-tv/tree/main/.claude/skills/speckit-git-commit
Command: npx skills add https://github.com/arosenkranz/kranz-tv --skill speckit-git-commit-arosenkranz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual workflows in Spec Kit often miss committing changes, leading to diverging state and lost work.

Core Features & Use Cases

  • Automatically detect hook events and determine when to commit
  • Read per-event configuration from .specify/extensions/git/git-config.yml
  • Stage all changed files and perform git commit with a configurable message
  • Works with Bash and PowerShell execution paths for cross-platform use
  • Supports graceful degradation when Git is unavailable or no changes exist

Quick Start

Enable auto-commit by configuring the git extension and then run your Spec Kit command as usual to auto-commit changes after each hook.

Frequently Asked Questions about speckit-git-commit

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

FAQPage Schema
How do I automatically commit changes after running Spec Kit commands?▼

To auto-commit after Spec Kit commands, configure the git extension within your .specify directory structure. It reacts to hook events like after_specify, reads git-config.yml, stages all changed files, and performs a git commit with a default or custom message.

Can I use git hooks to auto-commit in both Bash and PowerShell environments?▼

Yes, automated git commit hooks work with both Bash and PowerShell execution paths. This cross-platform support allows the auto-commit mechanism to function seamlessly whether your Spec Kit project runs on Unix or Windows systems.

What happens to the auto-commit process if Git is unavailable or there are no changes?▼

If Git is unavailable or there are no uncommitted changes, the auto-commit process gracefully skips the operation. This ensures your Spec Kit workflow continues without interruption or errors when conditions are not met.

How do I configure a custom commit message for Spec Kit hook events?▼

You can configure custom commit messages within the per-event git-config.yml file located in the .specify/extensions/git/ directory. The auto-commit extension reads this configuration to apply your specified message during the git commit.

Why do my Spec Kit workflow changes keep getting lost without manual commits?▼

Spec Kit workflows often miss manual commits, which leads to diverging state and lost work. Automating commits through after_specify or before_plan hook events ensures all changed files are staged and committed immediately after commands complete.