What problem does it solve?
Speckit workflows often produce modified files, and manual staging/committing after each run wastes time and increases the chance of forgetting changes.
Core Features & Use Cases
- Hook-based auto-commit: Automatically stages and commits changes after a Spec Kit command finishes, driven by the triggering hook event (for example, after_specify or before_plan).
- Configurable enablement and commit messaging: Uses .specify/extensions/git/git-config.yml to enable/disable commits per event, with a fallback to a default setting and optional per-event message overrides.
- Graceful degradation: Skips committing when Git is unavailable, when the directory is not a Git repository, when config is missing, or when there are no uncommitted changes.
Use case: After running a Spec Kit command that updates specifications or implementation artifacts, the skill ensures those updates are committed consistently with an event-appropriate message so your history stays clean.
Quick Start
Add the desired auto_commit settings in .specify/extensions/git/git-config.yml to enable commits for the hook event you use most, then run your Spec Kit command to have changes automatically staged and committed.