speckit-git-commit

To auto-commit Spec Kit changes, you can use a hook that triggers after commands like after_specify, before_plan, and after_implement. It automatically commits uncommitted changes to maintain a clean project history.

Automating git commits for Spec Kit workflows is best handled by hooking into the project lifecycle to auto-commit changes post-command. This enforces a configuration-driven activation and per-event toggles to satisfy git workflow requirements.

You configure git auto-commit settings for Spec Kit projects by editing the .specify/extensions/git/git-config.yml file. This configuration file allows per-event control and lets you set a default commit message.

No, the Spec Kit git auto-commit hook includes safeguards that skip the process if there are no changes or if Git is not available. It only commits uncommitted changes post-command to maintain a clean project history.

Yes, you can toggle specific git commit hooks for different Spec Kit events. The system supports per-event toggles via the git-config.yml file, allowing you to enable or disable hooks like after_specify, before_plan, and after_implement independently.