speckit-git-commit

Stage and commit working directory changes after Spec Kit hook events.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-git-commit-congtrinhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/Congtrinhh/sholy-be/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-git-commit-congtrinhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit workflows often produce modified files, and manual staging/committing after each run wastes time and increases the chance of forgetting changes.

Core Features & Use Cases

  • Hook-based auto-commit: Automatically stages and commits changes after a Spec Kit command finishes, driven by the triggering hook event (for example, after_specify or before_plan).
  • Configurable enablement and commit messaging: Uses .specify/extensions/git/git-config.yml to enable/disable commits per event, with a fallback to a default setting and optional per-event message overrides.
  • Graceful degradation: Skips committing when Git is unavailable, when the directory is not a Git repository, when config is missing, or when there are no uncommitted changes.

Use case: After running a Spec Kit command that updates specifications or implementation artifacts, the skill ensures those updates are committed consistently with an event-appropriate message so your history stays clean.

Quick Start

Add the desired auto_commit settings in .specify/extensions/git/git-config.yml to enable commits for the hook event you use most, then run your Spec Kit command to have changes automatically staged and committed.

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 Spec Kit changes after a hook event?

To auto-commit Spec Kit changes, configure the auto_commit settings in .specify/extensions/git/git-config.yml and run your Spec Kit command. The skill stages and commits working directory changes automatically once the hook event completes.

What is the best way to manage Git commits for Spec Kit workflows?

Managing Git commits for Spec Kit workflows is best handled by hook-driven auto-commit scripts. They ensure consistent, event-appropriate commit messages for updated specifications or artifacts, keeping your project history clean without manual staging.

Do I need a specific project structure to enable Spec Kit auto-commit?

You need a .specify project structure with a configured .specify/extensions/git/git-config.yml file to enable Spec Kit auto-commit. The appropriate bash or PowerShell script must also run with the resolved event name to satisfy conditional enablement.

Can I configure different commit messages for each Spec Kit hook event?

You can configure different commit messages for each Spec Kit hook event using the .specify/extensions/git/git-config.yml file. This configuration allows per-event message overrides with a fallback to a default setting.

What happens if Git is unavailable or there are no uncommitted changes in my Spec Kit project?

If Git is unavailable, the directory is not a repository, config is missing, or there are no uncommitted changes, the auto-commit script gracefully skips committing. This graceful degradation prevents workflow errors during Spec Kit execution.