speckit-git-commit

Stage and commit changes after Spec Kit commands using git-config.yml.

Updated May 16, 2026
One-click install
npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-git-commit-weihanli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/WeihanLi/Spark.OpenXml/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-git-commit-weihanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically stage and commit all changes after a Spec Kit command completes.

Core Features & Use Cases

  • Hooks into the Spec Kit command lifecycle to run git add . and git commit when auto_commit is enabled.
  • Looks up event names (after_specify, before_plan, after_implement) and supports a per-event message override.
  • Gracefully handles missing Git or no changes by skipping with a clear notice.

Quick Start

Configure your git integration by editing .specify/extensions/git/git-config.yml to enable auto_commit for default and any specific events, then run a Spec Kit command to see automatic commits occur.

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?

To auto-commit changes after Spec Kit commands, configure the .specify/extensions/git/git-config.yml file to enable auto_commit, which triggers automatic git add and git commit operations upon command completion.

Can I customize the git commit message for different Spec Kit events?

Yes, you can customize the git commit message for Spec Kit events. The skill looks up event names like after_specify and before_plan, supporting per-event message overrides configured in your git-config.yml file.

Does the Spec Kit auto-commit skill work if Git is not installed?

The Spec Kit auto-commit skill gracefully handles missing Git by skipping the commit process and providing a clear notice, ensuring your Spec Kit workflow continues without interruption when Git is unavailable.

What happens when there are no file changes to commit after a Spec Kit run?

When there are no file changes to commit after a Spec Kit run, the skill gracefully skips the commit step and outputs a clear notice, preventing empty commits in your version control history.

How to configure Spec Kit to stage and commit repository content automatically?

Configure Spec Kit to stage and commit automatically by editing .specify/extensions/git/git-config.yml to enable auto_commit for default or specific events, then run a Spec Kit command to trigger git add and git commit.