speckit-git-commit

You can automatically commit Git changes by configuring the `.specify/extensions/git/git-config.yml` file to enable `auto_commit` for specific hook events like `after_specify`. The system then stages and commits uncommitted changes automatically when those Spec Kit command hooks fire.

If there are no uncommitted changes when the auto-commit hook runs, the system gracefully skips the `git add` and `git commit` execution. It detects the clean working directory and skips the operation with an informational message rather than failing.

Yes, you can configure different auto-commit behaviors by setting event-specific keys within `.specify/extensions/git/git-config.yml`. The system selects the correct event key during the hook trigger and falls back to the `auto_commit.default` setting if a specific event configuration is missing.

Yes, you need an initialized Git repository to use Spec Kit auto-commit functionality. The system gracefully degrades by skipping the commit process with a warning if Git is unavailable or if the current working directory is not recognized as a valid repository.

Commit messages for automated Spec Kit check-ins are generated using the per-command configured `message` property defined in the `git-config.yml` file. If no custom message is provided for the specific event, the system applies a sensible default message automatically.

Spec Kit skips the auto-commit process when the configuration file is missing because automatic commits are disabled by default. This graceful degradation prevents unintended Git operations unless you explicitly create the file and set `auto_commit.enabled: true`.