speckit-git-commit

Auto-commit Spec Kit changes after specify lifecycle events using git-config.yml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents Spec Kit workflow outputs from being left uncommitted by automatically creating a git commit after the relevant command finishes, based on your configured rules.

Core Features & Use Cases

  • Event-aware auto-commit: Selects the correct hook event (for example, after_specify or before_plan) from the hook context.
  • Config-driven enablement and messaging: Reads .specify/extensions/git/git-config.yml to decide whether a commit should run and which commit message to use, including per-event overrides and a default fallback.
  • Change-only commits with graceful skips: Stages and commits only when there are uncommitted changes; otherwise it skips with a warning/message, including when git isn’t available or the config is missing.

Quick Start

Ask your AI to run the Spec Kit command in a project that contains a .specify/ directory and configure .specify/extensions/git/git-config.yml with auto_commit enabled for the event you want to commit.

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 workflow outputs to git?

To auto-commit Spec Kit outputs, this skill runs git add and git commit after lifecycle events like after_specify or before_plan, capturing generated changes automatically without manual git steps.

Does the auto-commit hook require a specific project setup?

Yes, the auto-commit hook requires a project containing a .specify/ directory and the git extension config file located at .specify/extensions/git/git-config.yml to read auto_commit settings.

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

You configure commit messages by editing .specify/extensions/git/git-config.yml, where you can define optional per-event message overrides or rely on a default fallback message for the auto-commit.

What happens if there are no uncommitted changes when the Spec Kit hook runs?

When no uncommitted changes exist, the auto-commit process gracefully skips the git commit step and issues a warning message, avoiding empty commits in your version control history.

Can I use Spec Kit auto-commit if the git config file is missing?

No, if the git extension config file is missing, the auto-commit skill cannot read the auto_commit settings and will gracefully skip the commit, including scenarios where git isn't available.