What problem does it solve? Running Spec Kit commands like specify, plan, or implement leaves uncommitted changes in your working tree, forcing you to manually stage and commit after every step. This Skill automates that bookkeeping so each specification milestone is captured in Git history without manual effort. ## Core Features & Use Cases - Hook-Based Auto-Commit: Runs as a before/after hook on Spec Kit commands (e.g., after_specify, before_plan) and commits pending changes with a configured message. - Per-Event Configuration: Reads .specify/extensions/git/git-config.yml to enable or disable auto-commit per command event, with custom commit messages and a global default toggle. - Graceful Degradation: Skips safely when Git is unavailable, the directory is not a repository, the config file is missing, or there are no changes to commit. - Use Case: After running /speckit.specify to draft a new feature specification, the hook detects the after_specify event, finds it enabled in the config, and commits the new spec files with the message "[Spec Kit] Add specification". ## Quick Start Enable auto_commit in .specify/extensions/git/git-config.yml and ask the agent to run the auto-commit script for the current hook event after your next Spec Kit command.