git-commit-helper

Analyze staged diffs and generate conventional commit messages.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Pixel-Process-UG/superkit-agents --skill git-commit-helper-pixel-process-ug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/Pixel-Process-UG/superkit-agents/tree/main/templates/skills/git-commit-helper
Command: npx skills add https://github.com/Pixel-Process-UG/superkit-agents --skill git-commit-helper-pixel-process-ug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers adhere to conventional commit standards, ensuring clear, consistent, and machine-readable commit messages, which streamlines versioning and changelog generation.

Core Features & Use Cases

  • Conventional Commits: Guides users through creating commit messages that follow the type(scope): description format.
  • Semantic Versioning: Assists in determining appropriate version bumps (MAJOR, MINOR, PATCH) based on commit content.
  • Changelog Generation: Provides guidelines for mapping commit types to changelog sections.
  • Commit Quality: Offers checklists and anti-pattern identification to improve commit message quality.
  • Use Case: A developer finishes a bug fix and needs to commit their changes. They use this skill to ensure the commit message is correctly formatted, specifies the type (fix), scope (api), and provides a clear description, while also considering if this fix warrants a patch version bump.

Quick Start

Use the git commit helper to generate a conventional commit message for 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 write conventional commit messages for Git?

To write conventional commit messages, structure them as type(scope): description. This Skill guides you through classifying commit types, defining scopes, and composing imperative, concise messages based on your staged diffs.

How do conventional commits map to semantic versioning bumps?

Conventional commits map directly to semantic versioning by triggering MAJOR, MINOR, or PATCH increments. This Skill analyzes your commit content and breaking changes to determine the appropriate version bump.

What is the correct format for a breaking change commit message?

A breaking change commit message follows standard conventional format but requires special handling. This Skill helps identify breaking changes and ensures they are properly documented within your structured commit message.

How do I generate a changelog from conventional commits?

To generate a changelog from conventional commits, map commit types to specific changelog sections. This Skill provides guidelines for structuring your commit history to streamline automated changelog generation.

What are common anti-patterns when formatting Git commit messages?

Common Git commit anti-patterns include non-imperative language and unclear descriptions. This Skill identifies these anti-patterns and provides checklists to improve your commit message quality.