skills.rest
rbkayz
rbkayzCOMMUNITY
Explore all skills by this author →
Website𝕏@rbkayzGitHub

git-commit-helper

Generate conventional commit messages from diff summaries and user intent.

Updated Feb 16, 2026
Search Tags:#git#developer tools#code review#commit#conventional commits
One-click install
npx skills add https://github.com/rbkayz/gitskills --skill git-commit-helper-rbkayz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/rbkayz/gitskills/tree/main/samples/git-commit-helper
Command: npx skills add https://github.com/rbkayz/gitskills --skill git-commit-helper-rbkayz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers generate conventional commit messages by providing a summary of changes and the intent behind them.

Core Features & Use Cases

  • Conventional Commits: Generates commit messages adhering to the Conventional Commits specification.
  • Intent-Based Generation: Creates messages based on a provided summary of changes and the developer's intent.
  • Use Case: After making changes to a feature, a developer can provide a summary like "Added user authentication" and an intent like "Implement new login flow" to get a well-formatted commit message like "feat: Implement new login flow (Added user authentication)".

Quick Start

Use the git-commit-helper skill to generate a commit message with a diff summary of 'Fixed a bug in the user profile page' and an intent of 'resolve critical issue'.

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 a git diff?▼

To generate conventional commit messages, provide the skill with a natural language summary of your code changes and your intent. It outputs a structured commit message like "feat: Implement new login flow" based on that input.

What is the conventional commits specification for software development?▼

The conventional commits specification standardizes commit messages using structured prefixes like "feat" or "fix". This skill enforces those guidelines by formatting your diff summaries and intent into compliant commit messages.

How do I write a structured git commit message after fixing a bug?▼

Write a structured git commit message by providing a summary like "Fixed a bug in the user profile page" and an intent like "resolve critical issue". The skill synthesizes these into a formatted conventional commit.

Do I need to provide a raw git diff to create a conventional commit?▼

You do not need to provide a raw git diff. The skill requires natural language input describing the changes made and the purpose of the commit to generate the formatted conventional commit message.

Can I use intent-based generation for code review commit messages?▼

Yes, intent-based generation creates code review commit messages by combining your stated intent with a diff summary. This ensures the resulting conventional commit accurately reflects both the technical changes and the developer's purpose.

Related Skills

Explore More Software Engineering Skills→
marinkobabicmarinkobabic

aif-commit

Generate conventional commit messages from staged Git diffs.

Community
Intermediate
royhenengelroyhenengel

git-pushing

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

Community
Intermediate
matteingmatteing
56

git

Validate commit messages against the Conventional Commits specification.

Community
Intermediate
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced