git-commits

Generate Conventional Commits messages and require user approval before git add and commit.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/pepeccz/msi-a --skill git-commits-pepeccz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commits
Source: https://github.com/pepeccz/msi-a/tree/main/skills/git-commits
Command: npx skills add https://github.com/pepeccz/msi-a --skill git-commits-pepeccz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates standardized Git commit messages following the Conventional Commits specification, reducing ambiguity and manual editing during code reviews.

Core Features & Use Cases

  • Enforces Conventional Commits format for all commits.
  • Suggests type, scope, and description based on changes.
  • Requires explicit user approval before executing git add and git commit to prevent unintended changes.
  • Supports typical workflows: feature work, bug fixes, docs updates, and chores.

Quick Start

Ask me to generate a conventional commit message for the current changes and wait for your approval before executing the commit.

Frequently Asked Questions about git-commits

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

FAQPage Schema
How do I automate conventional commits in git?

Automating conventional commits in git involves generating standardized messages that enforce the Conventional Commits specification, suggesting type, scope, and description based on changes. This Skill automates that formatting and requires explicit user approval before executing git add and git commit.

What is the conventional commits format for version control?

The conventional commits format for version control structures commit messages with specific types, scopes, and descriptions to standardize code changes. This automation enforces that format, reducing ambiguity and manual editing during code reviews for feature work, bug fixes, docs updates, and chores.

How do I require approval before running git add and git commit?

Requiring approval before running git add and git commit prevents unintended changes from entering version control. This Skill pauses the commit workflow to present the suggested conventional commit message and waits for your explicit approval before executing any git commands.

Does this git commit automation work for bug fixes and feature updates?

Yes, this git commit automation works for typical workflows including feature work, bug fixes, docs updates, and chores. It suggests the appropriate conventional commit type and scope based on the detected code changes to maintain a clean project history.

Can I review the commit message before the automation executes git commit?

Yes, you can review the commit message before the automation executes git commit. The workflow generates the conventional commit message suggestion and explicitly waits for your approval before running git add and git commit to prevent unintended changes.