speckit-git-commit

Automatically stage and commit changes after Spec Kit workflow commands.

8|1|Updated Sep 19, 2008
One-click install
npx skills add https://github.com/juvenal/openrender --skill speckit-git-commit-juvenal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-commit
Source: https://github.com/juvenal/openrender/tree/main/.cursor/skills/speckit-git-commit
Command: npx skills add https://github.com/juvenal/openrender --skill speckit-git-commit-juvenal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually committing changes after every Spec Kit command is tedious and easy to forget, leading to messy, uncommitted work and lost progress in your specification and implementation workflows.

Core Features & Use Cases

  • Automated Post-Command Commits: Automatically stages and commits all uncommitted changes immediately after any Spec Kit command finishes running, eliminating manual git steps.
  • Configurable Behavior: Supports per-command enable/disable toggles and custom commit messages via a simple YAML config file, so you can tailor commit behavior to your team's workflow standards.
  • Use Case: When building a new feature with Spec Kit, you run commands to create a specification, generate an implementation plan, and write code. This skill automatically commits each step with a relevant message, giving you a clean, traceable version history without interrupting your work.

Quick Start

Invoke the speckit-git-commit skill to automatically stage and commit all uncommitted changes after any 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 Spec Kit changes to streamline version control?

To auto-commit Spec Kit changes, you need a valid Git repository with a .specify/ directory. The workflow automatically stages and commits all uncommitted changes immediately after any Spec Kit command finishes running.

Can I configure custom commit messages for Spec Kit workflow commands?

Yes, you can configure custom commit messages and enable or disable auto-commit behavior per-command. You control these settings using an optional git-config.yml file in your project.

Do I need a specific Git repository setup to automate Spec Kit commits?

Yes, automating Spec Kit commits requires a valid Git repository containing a .specify/ directory. This ensures the workflow can accurately track and commit specification, planning, and implementation changes.

What is the best way to track Spec Kit specification and implementation progress in Git?

The best way to track Spec Kit progress is using automated post-command commits. This method stages and commits changes after each specification, planning, and implementation step to maintain a clean, traceable version history.

Why should I automate version control for Spec Kit workflows instead of committing manually?

Automating version control prevents messy, uncommitted work and lost progress. Manually committing changes after every Spec Kit command is tedious and easy to forget, whereas automation ensures consistent commit tracking without interrupting your work.