skills.rest
TranVanTienDat
TranVanTienDatCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generates Conventional Commits messages by analyzing git diffs and staging changes.

Updated Mar 26, 2026
Search Tags:#git#version control#commit#conventional commits#staging#diff#commit message
One-click install
npx skills add https://github.com/TranVanTienDat/Milkyway --skill git-commit-tranvantiendat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/TranVanTienDat/Milkyway/tree/main/apps/storefront/.agents/skills/git-commit
Command: npx skills add https://github.com/TranVanTienDat/Milkyway --skill git-commit-tranvantiendat

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 - Automatic Type and Scope Detection: Analyzes staged or working-tree diffs to infer whether a change is a feat, fix, refactor, docs update, or another conventional type, along with the affected module scope. - Smart Staging and Grouping: Stages files individually, by pattern, or interactively so each commit contains one logical change, while warning 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 assistant to commit your changes and receive a properly formatted message like fix(auth): correct token refresh logic without writing it yourself. ## Quick Start Ask the assistant to commit my current changes with a Conventional Commits 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 Commits message automatically?▼

Stage your changes or leave them in the working tree, then ask the assistant to commit. It runs git diff and git status to analyze the changes, infers the type and scope, and executes git commit with a properly formatted message.

What commit types does Conventional Commits support?▼

The supported types are feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. Each type maps to a specific change purpose, 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.

Can it prevent committing secrets like .env files?▼

Yes, the workflow explicitly warns against committing secrets such as .env files, credentials.json, or private keys during the staging step. You should review staged files before confirming the commit.

What happens if a git hook fails during commit?▼

If a commit fails due to hooks, the guidance is to fix the underlying issue and create a new commit rather than amending. The skill never bypasses hooks with --no-verify unless you explicitly request it.

Related Skills

Explore More Software Engineering Skills→
jaqgjaqg

git-sync

Group modified and untracked files into logical git commits and print the command sequence.

Community
Intermediate
awfixers-stuffawfixers-stuff

impl-review

Check out a pull request branch, apply reviewer feedback, and push changes.

Official
Advanced
MolcajeteAIMolcajeteAI
2

pre-commit-hooks

Configure Husky and lint-staged pre-commit hooks for automated code quality checks.

Official
Intermediate
laicluselaicluse
4

commit-all-the-things

Groups all uncommitted git changes into logical commits with descriptive messages.

Official
Intermediate