commit

Analyze Git changes and generate descriptive atomic commit messages.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/mikanfactory/dotfiles --skill commit-mikanfactory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mikanfactory/dotfiles/tree/main/home/dot_claude/skills/commit
Command: npx skills add https://github.com/mikanfactory/dotfiles --skill commit-mikanfactory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating well-defined, atomic Git commits, ensuring your commit history is clean and manageable.

Core Features & Use Cases

  • Automated Commit Splitting: Divides changes into logical, atomic commits.
  • Descriptive Commit Messages: Generates clear and concise messages for each commit.
  • Use Case: After making several unrelated changes to your codebase, use this Skill to automatically separate them into distinct commits, each addressing a specific feature or bug fix.

Quick Start

Use the commit skill to create atomic git commits for all staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create atomic git commits from multiple unrelated changes?

To create atomic git commits, this Skill analyzes your staged changes and automatically splits them into logical segments, generating descriptive commit messages for each distinct feature or bug fix.

What is the best way to automate commit splitting for version control?

Automating commit splitting for version control is achieved by using the git-commit-splitter agent, which analyzes your codebase changes and divides them into manageable, atomic commits with clear messages.

Why should I use atomic commits in my development workflow?

Atomic commits keep your version control history clean and manageable by ensuring each commit addresses a specific feature or bug fix, which simplifies code review and logical change segmentation.

Does this automated commit message generator work with staged changes only?

Yes, this automated commit message generator processes your staged changes to analyze logical differences and applies git commands to segment them into distinct, atomic commits.

Can I use this to prepare code review submissions with clean version control history?

Yes, you can use this to prepare code review submissions because it organizes unrelated codebase changes into distinct, atomic commits, ensuring a clean and manageable version control history.

When should I avoid automating git commit creation?

You should avoid automating git commit creation when your staged changes are already highly cohesive or when manual logical change segmentation is necessary to capture complex dependencies accurately.