speckit-git-commit

Stage and commit changes after Spec Kit commands complete.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Auto-commit after spec-kit commands to keep repositories in sync with the workflow.
  • Reads per-event configuration from .specify/extensions/git/git-config.yml and falls back to a default setting.
  • Safely commits only when there are unstaged changes, with warnings when git is unavailable or repository context is missing.

Quick Start

Enable auto-commit in the git config and then run any Spec Kit command to automatically commit changes upon completion.

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 auto-commit changes after spec-kit commands by enabling the hook in .specify/extensions/git/git-config.yml. It stages and commits uncommitted changes automatically upon command completion, falling back to the auto_commit.default setting if specific events are unconfigured.

What is the best way to keep my git repository in sync with the spec-kit workflow?

Using an automated git hook to auto-commit changes after spec-kit commands keeps your repository in sync. It safely stages and commits modifications after events like after_specify or before_plan, ensuring workflow steps map directly to repository commits.

Does the spec-kit auto-commit hook require a specific git configuration?

The auto-commit hook reads per-event enablement from .specify/extensions/git/git-config.yml and falls back to auto_commit.default. It requires git to be available in the environment and only executes a commit when uncommitted changes are detected.

Why does the spec-kit auto-commit hook warn that it cannot commit changes?

The auto-commit hook issues warnings and skips committing when git is unavailable on your system or when the current directory lacks a valid git repository context. Ensure git is installed and you are inside a repository before running spec-kit commands.

Can I enable auto-commit for specific spec-kit workflow events only?

Yes, you can enable auto-commit for specific events like after_specify and before_plan. Configure the per-event enablement settings within the .specify/extensions/git/git-config.yml file to control exactly which workflow triggers trigger an automatic commit.