skills.rest
asd335w3d
asd335w3dCOMMUNITY
Explore all skills by this author →
GitHub

git-commit-helper

Analyze Git diffs to generate Conventional Commits messages.

Updated Mar 8, 2026
Search Tags:#git#workflow#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/asd335w3d/SKills --skill git-commit-helper-asd335w3d
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/asd335w3d/SKills/tree/main/.github/skills/git-commit-helper
Command: npx skills add https://github.com/asd335w3d/SKills --skill git-commit-helper-asd335w3d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of commit messages that adhere to the Conventional Commits specification, ensuring a clean and standardized commit history.

Core Features & Use Cases

  • Automated Commit Message Generation: Analyzes Git diffs to suggest commit messages based on changes.
  • Conventional Commits Compliance: Ensures messages follow the <type>(<scope>): <subject> format.
  • Commit Splitting Suggestions: Recommends splitting changes into multiple atomic commits when appropriate.
  • Use Case: After making several unrelated changes, you need to commit them but aren't sure how to structure the message. This Skill provides well-formatted suggestions, potentially splitting them into logical commits.

Quick Start

Generate a commit message for the current Git 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 git diffs automatically?▼

To generate conventional commit messages, this Skill analyzes your staged or working directory git diffs to automatically suggest messages following the <type>(<scope>): <subject> format. It identifies commit types like feat or fix based on the detected code changes.

What is the best way to split complex git changes into atomic commits?▼

The best way to split complex git changes into atomic commits is using this Skill, which analyzes your working directory changes and suggests splitting them into multiple logical, conventional commits when appropriate to maintain a clean history.

How do I structure a git commit message for code review?▼

To structure a git commit message for code review, this Skill parses your version control diffs and generates a standardized conventional commit message complete with types, scopes, subjects, and optional bodies or footers for clear communication.

Does this conventional commit generator work with unstaged working directory changes?▼

Yes, this conventional commit generator works with unstaged working directory changes as well as staged git diffs, analyzing the version control modifications to suggest appropriate commit types and scopes.

Can I include footers and bodies in my automatically generated conventional commits?▼

Yes, you can include optional bodies and footers in your automatically generated conventional commits. The Skill analyzes your git changes and suggests these additional message sections when the diff context requires more detailed documentation.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
royhenengelroyhenengel

git-pushing

Stage, commit, and push Git changes with conventional commit messages.

Community
Intermediate
leafcoderleafcoder
2

git-workflow

Standardize Git practices and collaboration workflows across GitHub and Gitee.

Community
Intermediate
SukbeomHSukbeomH
2

commit

Generates conventional commit messages from staged Git diffs with emojis, types, and scopes.

Community
Intermediate