skills.rest
AdeptMind
AdeptMindOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit-helper

Generate conventional commit messages from staged Git changes.

Updated Mar 12, 2026
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/AdeptMind/pr-emojis-in-slack --skill git-commit-helper-adeptmind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/AdeptMind/pr-emojis-in-slack/tree/main/.claude/skills/git-commit-helper
Command: npx skills add https://github.com/AdeptMind/pr-emojis-in-slack --skill git-commit-helper-adeptmind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of conventional commit messages, ensuring consistency and clarity in your Git history.

Core Features & Use Cases

  • Automated Commit Message Generation: Creates commit messages based on staged Git changes.
  • Conventional Commits: Adheres to the widely adopted conventional commit specification for better project management and automated changelog generation.
  • Use Case: After staging your code changes, use this Skill to generate a well-formatted commit message that includes the type, scope, and a concise summary, potentially with a body and footer for breaking changes or issue references.

Quick Start

Use the git-commit-helper skill to generate a conventional commit message for your staged changes.

Frequently Asked Questions about git-commit-helper

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

FAQPage Schema
How do I generate conventional commit messages from staged git changes?▼

To generate conventional commit messages from staged git changes, the Skill analyzes your staged files and diffs to determine intent and scope, then outputs a formatted message with type, summary, body, and footer.

What is the conventional commit format for breaking changes and issue references?▼

The conventional commit format for breaking changes and issue references uses a structured footer convention, placing breaking change notices and issue tracker references at the end of the commit body.

Can I use conventional commits for massive diffs and merge commits?▼

Yes, you can use conventional commits for massive diffs and merge commits. The Skill specifically handles these edge cases along with empty changesets and deletions to ensure valid commit formatting.

What's the best way to automate conventional commit types like feat, fix, and refactor?▼

The best way to automate conventional commit types like feat, fix, and refactor is to use a generator that analyzes staged diffs, automatically determining whether your modifications constitute a feature, fix, or chore.

Does the conventional commit generator support chore, docs, test, style, perf, ci, and build types?▼

Yes, the conventional commit generator supports chore, docs, test, style, perf, ci, and build types, alongside feat, fix, and refactor, adhering to summary line rules and body explanations.

Related Skills

Explore More Software Engineering Skills→
ThedouglerThedougler

git-commit

Generate conventional git commit messages with automated file staging.

Community
Intermediate
NodeJSmithNodeJSmith
1

mine.commit-push

Stage changes, generate commit messages, update changelogs, and push to Git.

Community
Advanced
githubgithub
37.6k

git-commit

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

Official
Intermediate
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic