speckit-git-commit

Automate Git staging and commits after Spec Kit commands.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill speckit-git-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT/tree/main/.agent/skills/speckit-git-commit
Command: npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill speckit-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

Automates Git history maintenance by automatically staging and committing changes after Spec Kit commands, eliminating manual follow-up commits and reducing drift.

Core Features & Use Cases

  • Automatically stage and commit changes after Spec Kit commands, ensuring changes are captured in Git.
  • Honors per-event configuration in .specify/extensions/git/git-config.yml, allowing after_specify to enable and customize the commit message.
  • Gracefully handles scenarios where Git is unavailable or no changes exist, emitting warnings instead of failing.

Quick Start

Execute a Spec Kit command and rely on automatic commits when auto-commit is enabled

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 after running spec kit commands?

To automate git commits after spec kit commands, this Skill auto-stages and commits changes by triggering scripts during after_specify and after_plan events. It requires a .specify/extensions/git/git-config.yml configuration file to enable and customize the workflow.

Can I customize the commit message for auto-commits triggered by spec kit events?

Yes, you can customize the auto-commit message for spec kit events. The Skill honors per-event configuration settings defined in the .specify/extensions/git/git-config.yml file, allowing you to specify custom messages for after_specify and after_plan hooks.

What happens if git is unavailable or there are no changes to commit after a spec kit command?

If git is unavailable or no changes exist after a spec kit command, the auto-commit process gracefully emits a warning instead of failing. This ensures your version-control workflow continues without interruption or broken hooks.

Do I need a specific configuration file to enable auto-commit for spec kit?

Yes, you need a .specify/extensions/git/git-config.yml configuration file to enable auto-commit. This file manages per-event toggles and allows you to define optional custom messages for the after_specify and after_plan events.

Which spec kit events trigger the automatic git add and commit workflow?

The automatic git add and commit workflow is triggered by after_specify and after_plan spec kit events. The Skill executes bash or PowerShell scripts to handle version-control staging and committing automatically after these specific commands.

Why should I automate git history maintenance after spec kit commands?

Automating git history maintenance after spec kit commands eliminates manual follow-up commits and reduces drift. By auto-staging and committing changes immediately, it ensures all modifications are captured in version-control without extra effort.