git-batch-commit

Categorize staged file changes and generate Conventional Commits messages.

557|80|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/cat-xierluo/legal-skills --skill git-batch-commit-cat-xierluo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-batch-commit
Source: https://github.com/cat-xierluo/legal-skills/tree/main/skills/git-batch-commit
Command: npx skills add https://github.com/cat-xierluo/legal-skills --skill git-batch-commit-cat-xierluo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill tackles the common issue of messy Git commit histories by automatically categorizing and splitting mixed changes into multiple, focused commits, making your project history clear and understandable.

Core Features & Use Cases

  • Automatic Categorization: Classifies changes into types like feat, fix, docs, chore, etc., based on file type and content analysis.
  • Focused Commits: Creates individual commits for each category, ensuring each commit has a single, clear purpose.
  • Use Case: After making changes to documentation, source code, and configuration files, instead of one large commit, this Skill will create separate commits for each, like docs: Update README, feat: Implement new feature, and config: Adjust settings.

Quick Start

Use the git-batch-commit skill to automatically group and commit your staged changes.

Frequently Asked Questions about git-batch-commit

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

FAQPage Schema
How do I organize a messy Git history with multiple file types in one commit?

To organize a messy Git history, this skill categorizes staged file modifications by analyzing file patterns and diff content. It splits mixed changes into multiple focused commits, such as separating documentation updates from source code features.

How do I automatically generate conventional commit messages for staged changes?

You can generate conventional commit messages automatically by using this skill to evaluate your staged files. It assigns appropriate commit types like feat, fix, or docs based on the analyzed file content and conventional commits guidelines.

Can I split mixed staged changes into separate commits based on file categories?

Yes, you can split mixed staged changes into separate commits. This skill automatically categorizes modifications into dependencies, documentation, features, fixes, refactoring, style, chores, tests, configurations, and licenses.

Does this automated commit categorization work without external dependencies?

Yes, automated commit categorization works without external dependencies. The skill operates independently using its internal scripts and references to analyze file patterns and generate descriptive commit messages.

What is the best way to categorize documentation and configuration updates in version control?

The best way to categorize documentation and configuration updates is using this skill to classify file modifications. It identifies specific file types and generates targeted commit messages like docs for documentation and config for settings.