speckit-git-commit

Automates git staging and committing after Spec Kit commands complete.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-git-commit-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/sethdavis512/iridium/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-git-commit-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running Spec Kit commands like specify, plan, or implement, developers must manually stage and commit the generated artifacts, which is repetitive and easy to forget. This Skill hooks into Spec Kit command lifecycle events and commits changes automatically based on configuration. ## Core Features & Use Cases - Hook-based auto-commit: Runs as a before/after hook on Spec Kit commands, detecting the event name (e.g., after_specify, before_plan) from the hook context. - Configurable per-event behavior: Reads .specify/extensions/git/git-config.yml to enable or disable commits per command and define custom commit messages, with a global default fallback. - Graceful degradation: Skips safely when Git is unavailable, the directory is not a repository, no config file exists, or there are no changes to commit. - Use Case: A team using Spec Kit wants every generated specification committed with the message '[Spec Kit] Add specification' right after the specify command runs, without any manual git commands. ## Quick Start Enable auto_commit in .specify/extensions/git/git-config.yml and ask the agent to run the auto-commit script with the current hook event name after your Spec Kit command finishes.

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 auto_commit in .specify/extensions/git/git-config.yml by setting default to true or enabling specific events like after_specify. The hook then runs the auto-commit script with the event name, staging and committing all changes automatically.

How to configure custom commit messages for Spec Kit hooks?

Add a message field under each event key in the auto_commit section of git-config.yml, such as message: '[Spec Kit] Add specification' under after_specify. If no per-command message is set, a default message is used.

Does the auto-commit hook work without a git repository?

No. If Git is unavailable or the current directory is not a repository, the hook skips execution with a warning instead of failing, so the Spec Kit workflow continues uninterrupted.

What happens if there are no changes to commit?

The hook detects the absence of uncommitted changes and skips the commit step with a message. It does not create empty commits or raise errors.

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. Event-specific keys override the global default, giving per-command control.