commit-helper

Analyze git changes to generate Conventional Commits style messages.

1|Updated Feb 5, 2026

Search Tags:#git #versioning #commit #commit-message #conventional-commits #breaking-change

Ready to run

npx skills add https://github.com/tygwan/ultra-codex-init --skill commit-helper-tygwan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-helper
Source: https://github.com/tygwan/ultra-codex-init/tree/main/.codex/skills/commit-helper
Command: npx skills add https://github.com/tygwan/ultra-codex-init --skill commit-helper-tygwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically craft conventional commit messages from code changes, and detect breaking changes to support proper versioning.

Core Features & Use Cases

Analyze changes and generate conventional commit messages that comply with the Conventional Commits specification
Detect potential breaking changes and indicate the required major version impact
Integrate with existing git workflows to streamline commits and documentation

Quick Start

Provide the current git diff or staged changes to generate a conventional commit message.

Frequently Asked Questions about commit-helper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a conventional commit message from my git diff?▼

To generate a conventional commit message, provide your current git diff or staged changes. The Skill analyzes code changes, categorizes them by type, detects breaking changes, and formats the output to comply with the Conventional Commits specification.

What is a conventional commit message and when do I need it?▼

A conventional commit message follows a standardized format categorizing changes by type, scope, and breaking impact. You need it to automate versioning and streamline documentation in software projects using the Conventional Commits specification.

Can conventional commits automatically detect breaking changes in my code?▼

Yes, conventional commits can detect breaking changes by analyzing your staged and unstaged code differences. The Skill identifies critical modifications and indicates the required major version impact for your project.

Does the commit message generator work with existing git workflows?▼

Yes, the commit message generator integrates with existing git workflows by analyzing staged and unstaged changes. It streamlines commits for features, fixes, docs updates, and refactors without disrupting your development process.

What's the best way to categorize code refactors and docs updates in a commit message?▼

The best way to categorize refactors and docs updates is by applying the Conventional Commits specification to your git diff. The analysis identifies the specific change type and suggests an appropriate scope and version impact.

Do I need to stage all my files to get an accurate commit message?▼

You do not need to stage all files because the analysis evaluates both staged and unstaged changes. Providing the current git diff allows the Skill to accurately detect features, fixes, and breaking changes for the commit message.