speckit-git-commit

Automatically stage and commit changes after Spec Kit commands.

3|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/opencue/colony --skill speckit-git-commit-opencue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/opencue/colony/tree/main/.claude/skills/speckit-git-commit
Command: npx skills add https://github.com/opencue/colony --skill speckit-git-commit-opencue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the commit process after executing Spec Kit commands, streamlining version control for Spec Kit-based projects.

Core Features & Use Cases

  • Automated Committing: Stages and commits changes automatically following Spec Kit commands.
  • Compatibility: Designed for projects structured with a .specify/ directory, leveraging Spec Kit's project structure.
  • Use Case: For a project that requires regular updates to specifications and implementation plans, this Skill can save time by eliminating the need for manual commits after each update.

Quick Start

After executing a Spec Kit command, let the Skill auto-commit your changes using the command: 'auto-commit <event_name>'

Frequently Asked Questions about speckit-git-commit

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

FAQPage Schema
How do I automatically commit changes after running Spec Kit commands?

To automatically commit changes after Spec Kit commands, use a script that stages and commits modifications in projects containing a .specify/ directory. Execute the command 'auto-commit <event_name>' to trigger the version control process post-command.

Do I need a specific directory structure to auto-commit Spec Kit project changes?

Yes, auto-committing Spec Kit changes requires a .specify/ directory in your project. Additionally, you must configure the process using the .specify/extensions/git/git-config.yml file to enable automatic version control post-commands.

What is the best way to streamline git version control for specification updates?

The best way to streamline git version control for specification updates is automating the commit process. This eliminates manual commits after each Spec Kit update by automatically staging and committing changes using the 'auto-commit <event_name>' command.

How does auto-commit work with Spec Kit's project structure?

Auto-commit works by integrating with Spec Kit's project structure through the .specify/ directory. After executing Spec Kit commands, it automatically stages and commits changes based on configurations defined in .specify/extensions/git/git-config.yml.

Can I use this auto-commit script without a .specify/extensions/git/git-config.yml file?

No, you cannot use this auto-commit script without the configuration file. The script requires .specify/extensions/git/git-config.yml to properly configure and execute automatic version control after Spec Kit commands complete.