git-commit

Generates conventional commit messages by analyzing git diffs and staging changes.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/QT-7274/dotfiles --skill git-commit-qt-7274
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/QT-7274/dotfiles/tree/main/git-commit
Command: npx skills add https://github.com/QT-7274/dotfiles --skill git-commit-qt-7274

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful git commit messages is tedious and often inconsistent across a team. This Skill analyzes your actual code changes and produces standardized Conventional Commits messages with the correct type, scope, and description automatically. ## Core Features & Use Cases - Diff-Based Message Generation: Inspects staged or working-tree diffs to determine the appropriate commit type (feat, fix, docs, refactor, etc.) and scope. - Intelligent Staging: Groups and stages files logically before committing, while guarding against committing secrets like .env files or credentials. - Breaking Change Support: Formats breaking changes with the ! marker or BREAKING CHANGE footer per the Conventional Commits specification. - Use Case: After finishing a bug fix across three files, ask the AI to commit your changes and it stages the files, detects the type as fix, and creates a properly formatted commit like fix(auth): correct token expiration check. ## Quick Start Ask the AI to commit my current changes with a conventional commit message based on the diff.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write a conventional commit message?▼

A conventional commit follows the format `<type>[optional scope]: <description>`, using types like feat, fix, docs, or refactor. This Skill analyzes your git diff to pick the right type and scope, then writes the description in present tense under 72 characters.

How to generate a commit message from git diff automatically?▼

The Skill runs `git diff --staged` or `git diff` plus `git status --porcelain` to inspect changes, then infers the commit type and scope from the modified files and code. It executes the commit with a single or multi-line message including optional body and footer.

What commit types does Conventional Commits support?▼

The supported types are feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. Each maps to a specific change category, such as feat for new features and fix for bug fixes.

How do I mark a breaking change in a commit message?▼

Add an exclamation mark after the type or scope, like `feat!: remove deprecated endpoint`, or include a `BREAKING CHANGE:` footer in the commit body explaining what behavior changed.

Does this Skill prevent committing secrets or unsafe git operations?▼

Yes. It explicitly blocks committing files like .env, credentials.json, and private keys. It also never updates git config, runs destructive commands like force push or hard reset, or skips hooks without an explicit user request.