speckit-git-commit

Automatically stages and commits changes after Spec Kit commands complete.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc --skill speckit-git-commit-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/Ab0umar/selrs.cc/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/Ab0umar/selrs.cc --skill speckit-git-commit-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about speckit-git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-commit changes after Spec Kit commands?▼

Enable the auto_commit section in .specify/extensions/git/git-config.yml, either globally with default: true or per event like after_specify. The hook then runs the auto-commit script, which stages all changes and commits with the configured message.

How do I configure different commit messages per Spec Kit command?▼

Add an entry under auto_commit in git-config.yml for each event, such as after_specify or after_plan, with enabled: true and a custom message field. Events without a specific key fall back to the auto_commit.default setting.

Does the auto-commit hook work on Windows with PowerShell?▼

Yes, the skill provides both Bash and PowerShell script variants. Run .specify/extensions/git/scripts/powershell/auto-commit.ps1 with the event name on Windows, or the bash equivalent on Unix-like systems.

What happens if Git is not installed or the config file is missing?▼

The hook degrades gracefully: it skips with a warning if Git is unavailable or the directory is not a repository, skips silently if no config file exists, and skips with a message when there are no changes to commit.

Can I enable auto-commit for only some Spec Kit commands?▼

Yes, set auto_commit.default to false and enable individual events like after_specify with enabled: true. Only the explicitly enabled hook events will trigger automatic commits.