speckit-git-commit

Automate Git commits after Spec Kit command events.

Updated May 29, 2026
One-click install
npx skills add https://github.com/juanca202/exercise-mobile --skill speckit-git-commit-juanca202
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/juanca202/exercise-mobile/tree/main/.cursor/skills/speckit-git-commit
Command: npx skills add https://github.com/juanca202/exercise-mobile --skill speckit-git-commit-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the commit of changes after a Spec Kit command is completed, streamlining the workflow for developers using Spec Kit in their projects.

Core Features & Use Cases

  • Automated Commit: Automatically stages and commits all changes after a Spec Kit command.
  • Event-Based Triggering: Executes on specific events like 'after_specify', 'before_plan', etc., based on the hook context.
  • Conditional Commit: Commits only if there are uncommitted changes, with configurable messages.
  • Graceful Degradation: Skips commit if conditions are not met or if Git is not available.

Quick Start

Run the command to commit changes after executing a Spec Kit command: .specify/extensions/git/scripts/bash/auto-commit.sh <event_name>

Frequently Asked Questions about speckit-git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commits after running Spec Kit commands?

You can automate git commits after Spec Kit commands by running a hook-based bash script that triggers on events like 'after_specify' to automatically stage and commit all uncommitted changes.

What are the requirements for setting up auto-commit with Spec Kit?

Setting up auto-commit requires a Git repository initialized with a Spec Kit project structure and specific configuration files to properly register the event-based hooks.

How does event-based triggering work for Git commit automation?

Event-based triggering executes commit actions by listening for specific Spec Kit lifecycle events, such as 'before_plan' or 'after_specify', ensuring changes are committed only at the correct workflow stages.

Can I configure commit messages when automating Git commits in Spec Kit?

Yes, you can configure commit messages when automating Git commits in Spec Kit, and the system will conditionally commit only if there are actual uncommitted changes present in the repository.

What happens if Git is not available during a Spec Kit auto-commit hook?

If Git is not available or required conditions are not met during a Spec Kit auto-commit hook, the script will gracefully degrade by skipping the commit action without breaking your workflow.