commit

Analyze git status and diffs to propose grouped conventional commit messages.

1|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/asermax/claude-plugins --skill commit-asermax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/asermax/claude-plugins/tree/main/katachi/skills/commit
Command: npx skills add https://github.com/asermax/claude-plugins --skill commit-asermax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze uncommitted changes and create grouped conventional commits.

Core Features & Use Cases

  • Analyze git status, staged diffs, and recent history to identify change groups.
  • Propose conventional commit messages (feat, fix, docs, chore, etc.) grouped by feature or change type.
  • Present a plan and await user confirmation before applying commits.

Quick Start

Analyze the current working tree, propose grouped conventional commits, and wait for your confirmation before committing.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I group uncommitted git changes into conventional commits?

To group uncommitted git changes into conventional commits, this Skill analyzes your working tree, staged diffs, and recent history, then proposes commit messages grouped by feature or change type. It presents a plan and awaits your confirmation before applying the staged commits.

What is the best way to automate conventional commit messages for multi-file changes?

Automating conventional commit messages for multi-file changes involves analyzing untracked changes and diffs to identify logical groups. This process proposes properly typed and scoped messages for features, bug fixes, docs updates, and chores, enabling staged commits for each logical group.

Can I analyze git status and untracked changes to propose commit messages automatically?

Yes, you can analyze git status and untracked changes to propose commit messages automatically. The Skill evaluates staged diffs and recent branch history to generate conventional commit types and scopes, presenting a structured commit plan for your review before execution.

Does this approach support staging commits for separate logical change groups?

Yes, this approach supports staging commits for separate logical change groups. By identifying related modifications across multi-file changes, it groups them into distinct conventional commits, allowing you to apply each logical group individually after confirming the plan.

How do I ensure my branch management uses proper conventional commit types and scopes?

To ensure branch management uses proper conventional commit types and scopes, this Skill identifies and groups changes based on features, bug fixes, docs, and chores. It analyzes recent history and diffs to propose messages with the correct types and scopes for your workflow.