speckit-git-commit

Stage and commit repository changes after Spec Kit hook events.

Updated May 18, 2026
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-git-commit-kamijeong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-git-commit-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually staging and committing updates after Spec Kit commands finish, helping keep workflow changes captured consistently.

Core Features & Use Cases

  • Hook-Based Automation: Runs after or before Spec Kit events such as after_specify or before_plan.
  • Config-Driven Behavior: Reads git auto-commit settings from the project configuration and respects global and per-event toggles.
  • Safe Commit Handling: Skips when Git is unavailable, the repo is missing, no config exists, or there are no changes to commit.
  • Use Case: A team uses Spec Kit to generate specifications and wants each completed step automatically committed with a consistent message.

Quick Start

Ask the skill to auto-commit the current Spec Kit changes after the specified hook event using the repository’s configured commit rules.

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 git changes after Spec Kit hook events?

Auto-committing git changes after Spec Kit hook events involves reading the project's git auto-commit configuration and executing the hook script to stage and commit specification, planning, and implementation updates automatically.

Can I use git hooks to automate staging and committing Spec Kit planning steps?

Yes, automating staging and committing Spec Kit planning steps uses hook-based automation that triggers after events like after_specify or before_plan, applying the repository's configured commit rules to capture workflow changes.

What happens to Spec Kit auto-commit if the git repository or configuration is missing?

Spec Kit auto-commit safely skips execution if the git repository or configuration is missing, ensuring no errors occur when Git is unavailable, no config exists, or there are no changes to commit.

How does config-driven auto-commit handle per-event git toggles for Spec Kit?

Config-driven auto-commit handles per-event git toggles for Spec Kit by reading global and per-event settings from the project configuration, ensuring commits only occur when enabled for the detected hook event.

Do I need to manually stage files when using event-driven commits for Spec Kit workflows?

No, manual staging is unnecessary for event-driven commits in Spec Kit workflows because the automation handles staging and committing repository changes automatically once the hook event completes.