skills.rest
alfredoperez
alfredoperezCOMMUNITY
Explore all skills by this author →
GitHub

speckit-git-commit

Automatically stage and commit Git changes after Spec Kit commands.

80|21|Updated Dec 2, 2025
Search Tags:#git#version control#commit#spec-driven development#spec kit
One-click install
npx skills add https://github.com/alfredoperez/speckit-companion --skill speckit-git-commit-alfredoperez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/alfredoperez/speckit-companion/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/alfredoperez/speckit-companion --skill speckit-git-commit-alfredoperez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically stages and commits changes in a Git repository after a Spec Kit command is executed, eliminating the need for manual commits.

Core Features & Use Cases

  • Automated Commit: Automatically commit changes after a Spec Kit command is executed, ensuring the latest changes are always saved.
  • Compatibility: Designed to work with projects structured with a .specify/ directory.
  • Configuration: Allows customization of commit behavior with a .specify/extensions/git/git-config.yml file.
  • Use Case: Ideal for teams using Spec Kit for spec-driven development, ensuring code consistency and version control without manual intervention.

Quick Start

After executing a Spec Kit command, the Skill will automatically commit changes with a default message.

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?▼

You can automatically commit changes after Spec Kit commands by using a script that stages and commits modifications in your Git repository, eliminating manual version control steps. It triggers automatically after command execution.

Do I need a specific directory structure to automate Git commits for spec-driven development?▼

Yes, automated Git commits for spec-driven development require a `.specify/` directory in your project. The automation is designed to recognize this Spec Kit structure to function correctly.

Can I customize the automated commit message for my Spec Kit project?▼

Yes, you can customize the automated commit behavior and messages by creating a configuration file at `.specify/extensions/git/git-config.yml` within your project directory to override default settings.

What is the best way to maintain version control consistency in spec-driven development?▼

The best way to maintain version control consistency in spec-driven development is to automate staging and committing changes immediately after Spec Kit commands execute. This ensures latest changes are always saved without manual intervention.

Why are my Git commits missing after executing Spec Kit commands?▼

Git commits may be missing if your project lacks the required `.specify/` directory structure or the `.specify/extensions/git/git-config.yml` configuration file is incorrectly set up, preventing the automated commit script from triggering.

Related Skills

Explore More Software Engineering Skills→
estaciolimaestaciolima

speckit-git-commit

Automate Git staging and commits after Spec Kit lifecycle events.

Community
Intermediate
TMI-appsTMI-apps
2

push

Validate and push committed Git changes to a remote repository.

Official
Intermediate
unipds-engenharia-de-ia-aplicadaunipds-engenharia-de-ia-aplicada
1.0k

speckit-git-commit

Stage and commit repository changes after Spec Kit commands complete.

Official
Intermediate
kerolos-saaidkerolos-saaid

speckit-git-commit

Automatically stage and commit Git changes after Spec Kit commands.

Community
Intermediate