speckit-git-commit

Automate Git staging and commits after Spec Kit lifecycle events.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-git-commit-estaciolima
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/estaciolima/idle-improvement-game/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-git-commit-estaciolima

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual overhead of staging and committing changes after executing Spec Kit commands, ensuring your repository history remains consistent and up-to-date without extra effort.

Core Features & Use Cases

  • Event-Driven Automation: Automatically triggers Git operations based on specific Spec Kit lifecycle events like after_specify or before_plan.
  • Configurable Behavior: Allows granular control over which events trigger a commit and what message is used via a centralized configuration file.
  • Use Case: When you run a specification command, the system automatically detects the completion of the task and commits the resulting specification files to your repository with a standardized message.

Quick Start

Configure the auto_commit section in your git-config.yml file to enable automatic commits for your desired Spec Kit events.

Frequently Asked Questions about speckit-git-commit

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

FAQPage Schema
How do I automate Git commits for Spec Kit lifecycle events?

You can automate Git commits for Spec Kit events by configuring the auto_commit section within a git-config.yml file, enabling automatic staging and committing of changes after lifecycle events.

What is event-driven version control for specification workflows?

Event-driven version control for specification workflows automatically stages and commits repository changes when lifecycle events occur, ensuring repository history stays synchronized without manual intervention.

Do I need a configuration file to trigger Git commits after Spec Kit commands?

Yes, you need a valid git-config.yml file located in the .specify/extensions/git/ directory to define which Spec Kit events trigger a commit and what commit message is applied.

Can I control which Spec Kit events trigger an automatic Git commit?

Yes, you can control which events trigger a Git commit by configuring the auto_commit section in your git-config.yml file, allowing granular control over event-specific commit behavior like after_specify or before_plan.

What's the best way to keep repository history consistent after automated specification tasks?

The best way to keep repository history consistent after automated specification tasks is using event-driven Git automation to automatically stage and commit the resulting specification files with standardized messages.