commit-helper

Generate Conventional Commits commit messages and split commits via interactive rebasing.

1|12|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/ChatAndBuild/chatchat-skills --skill commit-helper-chatandbuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-helper
Source: https://github.com/ChatAndBuild/chatchat-skills/tree/main/skills/commit-helper
Command: npx skills add https://github.com/ChatAndBuild/chatchat-skills --skill commit-helper-chatandbuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill assists in creating clear, focused commit messages and plans, improving code review and project maintainability.

Core Features & Use Cases

  • Focused Commit Messages: Generate concise, informative commit messages that help reviewers and future developers understand the intent of each change.
  • Commit Splitting: Identify and separate unrelated changes into distinct commits, enhancing code readability and maintainability.
  • Conventional Commits: Apply Conventional Commits standards to your commit messages for better integration with CI/CD pipelines and issue tracking tools.
  • Use Case: When you have a mix of feature additions, bug fixes, and documentation updates in a single codebase, this Skill helps you organize your commits effectively.

Quick Start

Run the commit-helper skill with the current diff to generate focused commit messages.

Frequently Asked Questions about commit-helper

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

FAQPage Schema
How do I write focused conventional commit messages for mixed code changes?

Generate focused conventional commit messages by providing your current code diff to create concise, review-friendly messages that separate unrelated changes into distinct commits for better maintainability.

What is the best way to split mixed feature and bug fix changes into separate git commits?

Splitting mixed changes into separate git commits involves identifying unrelated modifications and organizing them into distinct commits, which this tool accomplishes using interactive rebasing to enhance codebase readability.

Does commit-helper require git to apply Conventional Commits standards?

Yes, applying Conventional Commits standards requires git as a dependency to process your code changes and generate messages that integrate with CI/CD pipelines and issue tracking tools.

Can I use interactive rebasing to organize commits for better code review?

Yes, you can use interactive rebasing to organize commits for better code review, as this approach identifies and separates unrelated codebase changes into distinct, focused commit messages.

When do I need to split commits instead of creating a single commit message?

You need to split commits when a single codebase contains a mix of feature additions, bug fixes, and documentation updates, ensuring each distinct change receives a focused message for maintainability.