speckit-git-commit

Automates staging and committing Spec Kit hook events' repository changes with Git config support.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-git-commit-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-git-commit-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive manual step of staging and committing changes after Spec Kit hooks finish, keeping your repository history aligned with the command that triggered the update.

Core Features & Use Cases

  • Event-aware auto-commit: Detects the hook event name and chooses the matching commit behavior for after_specify, before_plan, and after_implement workflows.
  • Config-driven control: Reads git-config settings to enable or disable auto-commit globally or per event and customize the commit message.
  • Safe fallback behavior: Skips cleanly when Git is unavailable, the repository is not initialized, the config file is missing, or there are no changes to commit.

Quick Start

Use the speckit-git-commit skill to automatically stage and commit any repository changes after the current Spec Kit hook event completes.

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 Spec Kit hooks complete?

Auto-committing Spec Kit changes requires Git access and a companion Bash or PowerShell script to read .specify/extensions/git/git-config.yml, detect the triggering event, and stage uncommitted changes with event-specific commit messages.

Can I customize the commit message for different Spec Kit workflow events?

You can customize commit messages per event in git-config.yml for after_specify, before_plan, and after_implement hooks, allowing the auto-commit script to apply event-specific messages to staged changes.

Does the Spec Kit auto-commit script skip committing when there are no changes?

The auto-commit script safely skips committing when no uncommitted changes exist, when Git is unavailable, when the repository is uninitialized, or when the git-config.yml configuration file is missing.

How do I disable auto-commit for a specific Spec Kit hook event?

Disable auto-commit globally or per event by adjusting settings in git-config.yml, which the companion script reads to determine whether to skip committing for after_specify, before_plan, or after_implement workflows.

What configuration file is required to automate Git commits for Spec Kit projects?

Automating Git commits for Spec Kit projects requires the .specify/extensions/git/git-config.yml file to control auto-commit behavior and define event-specific messages for after_specify, before_plan, and after_implement workflows.