commit-helper

Name: commit-helper
Availability: InStock
Author: Zhao

Generate Conventional Commits messages with imperative subjects under 50 characters.

69|11|Updated Jan 10, 2026

Search Tags:#automation #git #workflow #commit #version-control #conventional-commits #message

Ready to run

npx skills add https://github.com/zhaono1/agent-playbook --skill commit-helper-zhaono1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-helper
Source: https://github.com/zhaono1/agent-playbook/tree/main/skills/commit-helper
Command: npx skills add https://github.com/zhaono1/agent-playbook --skill commit-helper-zhaono1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git commit messages are often inconsistent and hard to understand, making it difficult to review history and track changes. This skill enforces the Conventional Commits standard to produce clear, actionable messages that reflect the type and scope of each change.

Core Features & Use Cases

Generates commit messages that conform to the Conventional Commits specification (feat, fix, docs, style, refactor, perf, test, chore, ci, build).
Validates subject length (1-50 characters) and enforces imperative mood to improve readability.
Supports optional body content and scope to capture additional context for code reviews and history tracing.

Quick Start

Generate a conventional commit message for the current changes and present it for review before committing.

Frequently Asked Questions about 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 changes?▼

To generate conventional commit messages for git changes, this skill analyzes your current modifications and outputs a ready-to-use string formatted with the correct type, scope, and imperative subject under 50 characters.

What is the conventional commits specification for git workflow automation?▼

The conventional commits specification for git workflow automation standardizes commit messages using types like feat, fix, or chore, along with an optional scope and body to make version control history readable and actionable.

How to enforce a 50-character limit and imperative mood in git commit messages?▼

To enforce a 50-character limit and imperative mood in git commit messages, this skill validates subject length between 1-50 characters and structures the phrasing to directly reflect the applied change.

Does this commit message generator support optional body content and scope?▼

Yes, this commit message generator supports optional body content and scope, allowing you to capture additional context needed for code reviews and accurate history tracing alongside the primary subject.

What's the best way to automate version-control messages for code reviews?▼

The best way to automate version-control messages for code reviews is to generate standardized, conventional commit text that clearly identifies the change type and scope, ready for direct execution with git commit.

Can I use the generated commit message directly with git commit -m?▼

Yes, you can use the generated commit message directly with git commit -m because the skill returns a properly formatted, ready-to-use string that requires no manual editing before execution.