git-commit

Stage and commit repository changes after Spec Kit lifecycle events.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/eavichay/mycli --skill git-commit-eavichay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/git-commit
Command: npx skills add https://github.com/eavichay/mycli --skill git-commit-eavichay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the manual overhead of staging and committing changes after executing Spec Kit commands, ensuring your repository history stays perfectly synced with your development progress.

Core Features & Use Cases

  • Event-Driven Automation: Automatically triggers commits based on specific lifecycle events like after_specify or after_task_execute.
  • Configurable Messaging: Supports custom commit messages per event type or via direct command flags.
  • Use Case: When working on a large feature, use this to automatically checkpoint your progress with a descriptive message every time a task is completed, without needing to switch contexts to the terminal.

Quick Start

Invoke the git-commit skill to stage and commit changes for the after_specify event with a custom message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate git commits for Spec Kit lifecycle events?

To automate git commits for Spec Kit events, you can use a skill that triggers staging and committing changes automatically after specific lifecycle events like after_specify or after_task_execute. It requires a valid git environment and a configured .specify/extensions/git/git-config.yml file to manage event-specific commit behavior.

What is event-driven version control automation in a Spec Kit project?

Event-driven version control automation in a Spec Kit project removes manual overhead by automatically triggering git commits based on specific lifecycle events. This ensures your repository history stays perfectly synced with your development progress without needing to switch contexts to the terminal.

Do I need a specific configuration file to manage custom commit messages for Spec Kit workflows?

Yes, you need a configured .specify/extensions/git/git-config.yml file to manage event-specific commit behavior. This configuration supports custom commit messages per event type or via direct command flags, ensuring consistent version control checkpoints.

Can I use custom commit messages when automating version control checkpoints?

Yes, you can use custom commit messages when automating version control checkpoints. The automation supports configurable messaging per event type or via direct command flags, allowing you to automatically checkpoint progress with a descriptive message every time a task is completed.

What are the limitations of automating git staging and committing within a Spec Kit project structure?

The automation operates strictly within the context of a Spec Kit project structure. It requires a valid git environment and the .specify/extensions/git/git-config.yml file to function, meaning it cannot manage event-specific commit behavior outside of these configured Spec Kit lifecycle events.