speckit-git-commit

Stage and commit file changes after Spec Kit lifecycle events.

Updated May 31, 2026
One-click install
npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-git-commit-piklar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/Piklar/Rizza-60/tree/main/.agents/skills/speckit-git-commit
Command: npx skills add https://github.com/Piklar/Rizza-60 --skill speckit-git-commit-piklar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual overhead of staging and committing changes after executing Spec Kit commands, ensuring your repository history remains consistent and up-to-date without extra effort.

Core Features & Use Cases

  • Event-Driven Automation: Automatically triggers git operations based on specific Spec Kit lifecycle events like after_specify or after_implement.
  • Configurable Behavior: Allows granular control over auto-commit settings and custom commit messages via a centralized YAML configuration file.
  • Use Case: When working on a complex feature, use this skill to automatically commit your specification files immediately after the specify command finishes, keeping your documentation in sync with your code.

Quick Start

Trigger the speckit-git-commit skill by passing the current hook event name to the appropriate bash or powershell script.

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 Spec Kit lifecycle events?

You can automate git commits by triggering a script that monitors Spec Kit hook contexts like after_specify or after_implement and applies your defined git configurations to stage and commit changes automatically.

What is event-driven git commit automation for version control workflows?

Event-driven git commit automation is a process that triggers staging and committing operations automatically based on specific project lifecycle events, ensuring repository history remains consistent without manual overhead.

Do I need a specific configuration file to automate Spec Kit git operations?

Yes, you need a valid .specify/extensions/git/git-config.yml file to configure auto-commit settings and custom commit messages for automating Spec Kit git operations.

Can I customize commit messages when automating version control hooks?

Yes, you can customize commit messages when automating version control hooks by defining your preferred settings and message templates within a centralized YAML configuration file.

Does the Spec Kit git automation require local git binaries to run?

Yes, Spec Kit git automation requires access to local git binaries on your system to execute the staging and committing operations successfully.

When should I avoid automating git staging and commits in a workflow?

You should avoid automating git staging and commits if your project lacks a valid .specify/extensions/git/git-config.yml file or if local git binaries are unavailable on your system.