speckit-git-commit

Stage and commit code changes after Spec Kit commands complete.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-git-commit-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-git-commit
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-git-commit-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Determines the event name from the trigger context (e.g., after_specify or before_plan).
  • Checks .specify/extensions/git/git-config.yml for an auto_commit section and uses per-event keys or defaults.
  • Uses the per-command message if configured, otherwise a default commit message.
  • If enabled and there are uncommitted changes, runs git add . and git commit.

Quick Start

Run the appropriate auto-commit script with the event name to automatically commit changes after a Spec Kit command completes.

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 code changes after Spec Kit commands complete?

To auto-commit code changes after Spec Kit commands, the skill reads the trigger event and per-event configuration from git-config.yml to automatically stage and commit changes. It enforces commit discipline across project artifacts.

How do git hooks enforce commit discipline for project artifacts?

Git hooks enforce commit discipline by triggering auto-commit scripts during workflow events like after_specify or before_plan. The script checks for uncommitted changes and applies git add and commit operations automatically.

Do I need to configure git-config.yml to enable auto-commit for Spec Kit workflows?

Yes, you need to configure the auto_commit section in git-config.yml to enable auto-commit. The skill checks this file for per-event keys and messaging, falling back to default commit messages if specific ones are missing.

Can I customize commit messages for different Spec Kit hook events?

Yes, you can customize commit messages for different Spec Kit hook events by defining per-command messages in git-config.yml. If a specific message is not configured, the skill uses a default commit message.

What happens when there are no uncommitted changes during a Spec Kit auto-commit trigger?

When there are no uncommitted changes during a Spec Kit auto-commit trigger, the skill detects the empty state and skips the git add and commit operations entirely. It only performs commits when changes actually exist.