speckit-git-commit

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/luansilvadb/divi-app --skill speckit-git-commit-luansilvadb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/luansilvadb/divi-app/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/luansilvadb/divi-app --skill speckit-git-commit-luansilvadb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Reads per-event configuration from .specify/extensions/git/git-config.yml and falls back to default when needed.
  • Supports both Bash and PowerShell script paths for executing the auto-commit logic in hooks.
  • Gracefully skips if Git is unavailable or not a repository, ensuring safe operation.

Quick Start

Configure your Spec Kit project to enable auto-commit and run a Spec Kit command to observe automatic commits.

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 auto-commit after Spec Kit commands, enable the git hook to stage and commit changes automatically. It reads configuration from .specify/extensions/git/git-config.yml and runs git add . and git commit when a command completes.

Does the Spec Kit auto-commit hook work with both Bash and PowerShell?

Yes, the Spec Kit auto-commit hook supports both Bash and PowerShell execution paths. It applies to Spec Kit projects using .specify/extensions/git, ensuring cross-platform compatibility for post-command git operations.

What happens if Git is unavailable or the directory is not a repository?

If Git is unavailable or the directory is not a repository, the auto-commit hook gracefully skips execution. This ensures safe operation by preventing errors when running Spec Kit commands outside of version-controlled environments.

How do I configure auto-commit behavior for different Spec Kit events?

You configure auto-commit behavior by editing .specify/extensions/git/git-config.yml. The hook reads per-event configuration from this file and falls back to default settings when specific event configurations are not provided.

Why are my Spec Kit changes not automatically committed to my repository?

Changes may not auto-commit if the feature is disabled in .specify/extensions/git/git-config.yml or if the directory lacks a valid Git repository. The hook silently skips execution when Git is not detected to ensure safe operation.