git-commit

Analyze diffs and stage changes to generate conventional git commit messages.

2|1|Updated Feb 5, 2026

Search Tags:#git #bash #staging #interactive #conventional-commits #commit-messages #diff-analysis

Ready to run

npx skills add https://github.com/forgivesam168/ai-dev-workflow --skill git-commit-forgivesam168

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/forgivesam168/ai-dev-workflow/tree/main/skills/git-commit
Command: npx skills add https://github.com/forgivesam168/ai-dev-workflow --skill git-commit-forgivesam168

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps automate the creation of conventional git commits by analyzing diffs and staging changes to produce consistent, meaningful messages.

Core Features & Use Cases

Auto-detecting type and scope from changes to generate accurate commit prefixes.
Generate conventional commit messages from diffs to conform to the Conventional Commits spec.
Interactive commit workflow allowing overrides for type, scope, and description.
Intelligent file staging to group related changes into a single, logical commit.

Quick Start

Stage your changes, then run the commit flow to generate and apply a conventional message like <type>[scope]: <description>. Example: git commit -m "<feat>(ui): improve dashboard rendering"

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate conventional commit messages automatically from git diffs?▼

To generate conventional commit messages automatically, this Skill analyzes your staged git diffs to detect the type and scope, then produces a consistent message formatted as <type>[scope]: <description> without manual input.

Can I override the auto-generated type and scope for a conventional commit?▼

Yes, you can override the auto-generated type and scope during the interactive commit workflow, allowing you to manually adjust the commit prefix and description before finalizing the changes.

What is the best way to group related file changes into a single logical git commit?▼

The best way to group related changes is through intelligent file staging, which evaluates your diffs and stages only related modifications together to ensure safe, atomic, and logical commits.

Does this conventional commit workflow work with existing PR workflows?▼

Yes, the automated commit messaging applies across code changes in repositories and PR workflows, analyzing diffs to ensure commit messages conform to the Conventional Commits spec.