skills.rest
lettucebo
lettuceboCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Generates conventional commit messages by analyzing git diffs and repository history.

Updated Mar 25, 2026
Search Tags:#git#changelog#version control#commit#conventional commits#staging#commit message
One-click install
npx skills add https://github.com/lettucebo/Skills --skill git-commit-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/lettucebo/Skills/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/lettucebo/Skills --skill git-commit-lettucebo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful commit messages is tedious and often inconsistent across a team. This Skill analyzes your actual code changes and git history to produce standardized Conventional Commits messages with the correct type, scope, and description. ## Core Features & Use Cases - Automatic Type Detection: Inspects the diff and recent git history to choose the right commit type (feat, fix, refactor, docs, etc.), including the rule that fixes to already-committed features use fix rather than feat. - Intelligent Staging: Groups related changes into logical commits and stages files by path or pattern, while warning against committing secrets like .env files or credentials. - Message Generation: Produces imperative-mood descriptions under 72 characters, with body and footer sections for motivation, breaking changes, and issue references. - Use Case: After finishing a bug fix across several files, ask the agent to commit your changes and it will stage the relevant files, check history, and create a commit like fix(invoice): correct invoice number formatting with a proper body. ## Quick Start Ask the agent to commit my current changes with a conventional commit message based on the staged 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(scope): description, such as feat(auth): add JWT refresh token rotation. The type must be one of feat, fix, docs, style, refactor, perf, test, build, ci, chore, or revert, and the description uses imperative mood under 72 characters.

How do I choose between feat and fix commit types?▼

Check the git history for the affected files first. If the feature was already committed as feat, subsequent corrections use fix; if the new functionality is still uncommitted and submitted together, use feat for the primary change.

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 I commit multiple unrelated changes in one commit?▼

No, each commit should contain one logical change. Stage related files together using git add with specific paths or patterns, and split unrelated modifications into separate commits for a clean history.

What files should never be committed to git?▼

Never commit secrets such as .env files, credentials.json, or private keys. The skill explicitly checks for these during staging and warns before they enter the commit.

Related Skills

Explore More Software Engineering Skills→
codeaholicguycodeaholicguy
1.6k

dev-commit

Creates verified conventional git commits containing only intended changes.

Community
Intermediate
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
aram-devdocsaram-devdocs
6

review-changes

Dispatch five parallel agents to analyze pending code changes for security, performance, and architecture issues.

Community
Advanced
onbjergonbjerg
4

commit

Generates Conventional Commits messages from local change status and diff tools.

Community
Basic