speckit-git-commit

Stage and commit file changes after Spec Kit hook execution.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill speckit-git-commit-ayehiaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill speckit-git-commit-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the repetitive manual step of staging and committing changes after running Spec Kit commands, so your workflow stays fast and consistent.

Core Features & Use Cases

  • Hook-based auto-commit: Automatically stages and commits changes when a Spec Kit hook completes (for example after_specify or before_plan).
  • Config-driven behavior: Reads .specify/extensions/git/git-config.yml to enable/disable auto-commit per event and optionally customize commit messages.
  • Graceful skipping: Avoids failures when Git is unavailable, the directory is not a repository, no config exists, or there are no changes to commit.

Quick Start

Run Spec Kit in your project and ensure .specify/extensions/git/git-config.yml sets auto_commit.after_specify.enabled: true (and optionally a message) so the hook commits any resulting changes.

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 file changes after Spec Kit hook execution?

To automate git commits after Spec Kit hooks, configure `auto_commit.enabled: true` inside `.specify/extensions/git/git-config.yml` for events like after_specify, and the hook will stage and commit changes automatically.

How does Spec Kit hook configuration control git auto-commit behavior?

Spec Kit hook configuration controls git auto-commit by reading `.specify/extensions/git/git-config.yml`, where you enable or disable auto-commit per event and optionally customize the commit messages applied to staged changes.

What happens when Git is unavailable or there are no changes to commit in a Spec Kit project?

The auto-commit script gracefully skips execution without causing failures if Git is unavailable, the directory is not a repository, the config file is missing, or there are no uncommitted file changes.

Do I need a git-backed repository to use Spec Kit auto-commit hooks?

Yes, Spec Kit auto-commit hooks require a git-backed repository because the script directly stages and commits file changes within the existing version control structure after hook events complete.

Can I customize commit messages for different Spec Kit hook events?

Yes, you can customize commit messages for Spec Kit hook events by setting the optional `message` field alongside the `enabled` flag for each specific event inside the `.specify/extensions/git/git-config.yml` file.

What's the best way to automate version control for Spec Kit workflow changes?

The best way to automate version control for Spec Kit workflows is enabling config-driven auto-commit hooks that detect uncommitted changes and automatically stage and commit them after events like after_specify or after_implement.