Git Commit Helper

Generate git commit messages following the Conventional Commits specification.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/run6270/skill --skill git-commit-helper-run6270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Git Commit Helper
Source: https://github.com/run6270/skill/tree/main/git-commit-helper
Command: npx skills add https://github.com/run6270/skill --skill git-commit-helper-run6270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of git commit messages, ensuring they adhere to the Conventional Commits specification for better project history and automated changelog generation.

Core Features & Use Cases

  • Conventional Commits: Generates commit messages following the <type>(<scope>): <subject>\n\n<body>\n\n<footer> format.
  • Type Guidance: Provides a list of standard commit types (feat, fix, docs, etc.).
  • Use Case: When you've finished a new feature and need to commit your changes, this skill helps you craft a message that clearly indicates it's a 'feat' and describes the change concisely.

Quick Start

Use the Git Commit Helper skill to generate a commit message for a new feature that adds user authentication.

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 for git?

To generate conventional commit messages, the skill analyzes your git changes and formats them into the `<type>(<scope>): <subject>\ \ <body>\ \ <footer>` specification. It guides you through selecting standard types like feat, fix, or docs to ensure structured project history.

What are the standard commit types used in version control?

Standard commit types in version control include feat, fix, docs, and others defined by the Conventional Commits specification. The skill provides guidance on these types to clearly categorize changes, such as using feat for new features or fix for bug resolutions.

How do I analyze git changes before writing a commit message?

Analyzing git changes before writing a commit message requires running git commands like status and diff. The skill uses the output from these commands to understand your modifications, ensuring the generated message accurately describes the actual code changes.

Does the Git Commit Helper work for automated changelog generation?

Yes, the Git Commit Helper works for automated changelog generation by enforcing the Conventional Commits specification. Structured commit messages allow automated tools to parse your project history and generate accurate changelogs without manual intervention.

When do I need to use the Conventional Commits specification?

You need to use the Conventional Commits specification when you want a structured commit history for software development projects. It is essential for maintaining clear project logs and enabling automated changelog generation from your git commit messages.