speckit-git-commit

Auto-commit staged Spec Kit changes after hook events complete.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-git-commit-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-git-commit
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-git-commit-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from forgetting to stage and commit Spec Kit outputs by automating Git commits right after Spec Kit commands finish.

Core Features & Use Cases

  • Hook-based auto-commit: Triggers on specific Spec Kit hook events (for example, after_specify or before_plan) and uses the hook context to choose the commit behavior.
  • Config-driven control: Reads .specify/extensions/git/git-config.yml to enable auto-commit per event, with a default fallback and optional custom commit messages.
  • Safe operation: Detects whether Git is available and whether the working directory is a repository, then commits only when there are uncommitted changes.

Quick Start

Enable auto_commit in .specify/extensions/git/git-config.yml for the hook event you want and run Spec Kit so the extension stages and commits changes automatically when they exist.

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 Spec Kit changes to Git after a command finishes?

To auto-commit Spec Kit changes, enable the auto_commit setting in .specify/extensions/git/git-config.yml. The extension triggers event-specific bash or PowerShell scripts after hooks like after_specify complete, committing staged changes automatically when uncommitted changes exist.

What is hook-based auto-committing for Spec Kit directory layouts?

Hook-based auto-committing automatically stages and commits Spec Kit outputs by triggering on specific hook events like after_specify or before_plan. It reads the hook context to choose commit behavior and executes scripts only when Git is available and changes exist.

How do I configure custom commit messages for Spec Kit hook events?

Configure custom commit messages in .specify/extensions/git/git-config.yml. This configuration file enables auto-commit per event and allows optional custom commit messages, using a default fallback when specific messages are not provided.

Does the Spec Kit Git extension require a root SKILL.md entry to function?

Yes, the Spec Kit Git extension requires a root SKILL.md entry to function. It reads this entry alongside the .specify/extensions/git/git-config.yml file to determine auto-commit enablement and select commit messages for specific hook events.

What happens if Git is not available or there are no uncommitted changes?

If Git is not available or the working directory is not a repository, the auto-commit script does not execute. The extension safely detects repository status and commits only when uncommitted changes exist, preventing empty commits.