speckit-git-commit

To automatically commit Spec Kit files, you can use an auto-commit hook that triggers after events like after_specify or before_plan. It checks your project's git-config.yml settings and runs git add and commit if enabled.

The best way to stage and commit Spec Kit changes automatically is by using a hook-aware automation tool. It reads per-event messages from git-config.yml and executes git add . plus git commit when modifications exist.

No, the auto-commit hook requires a .specify/extensions/git/git-config.yml file to function. If the config is missing or Git is unavailable, the hook degrades gracefully and skips the commit with a warning.

Yes, you can customize commit messages for different Spec Kit hook events by defining per-event messages in your git-config.yml. The hook applies these custom messages and falls back to a default if none are provided.

When the auto-commit hook runs and finds no repository changes to commit, it gracefully skips the commit process. This prevents empty commits and ensures clean git history after Spec Kit commands.

Yes, Git must be installed and the directory must be a repository to use Spec Kit auto-commit hooks. The hook gracefully skips execution with a warning if Git is unavailable or the directory is not initialized.