commit

Analyze git status and diffs to group changes into logical commits.

Updated Aug 23, 2026

Search Tags:#git #commit #history #diff #message #segment

Ready to run

npx skills add https://github.com/mickaelyoshua/dev --skill commit-mickaelyoshua

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/mickaelyoshua/dev/tree/main/.claude-skills/commit
Command: npx skills add https://github.com/mickaelyoshua/dev --skill commit-mickaelyoshua

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers convert raw working tree changes into a clean, readable commit history that tells the story of the changes.

Core Features & Use Cases

Analyze git status and diffs to understand every change.
Group unrelated changes into separate commits to maintain a logical history.
Enforce concise, lowercase commit messages with no signatures or unnecessary footers.

Quick Start

Explain changes with git status and git diff, then commit each logical change with a short, lowercase message.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I convert raw git diffs into a clean commit history?▼

To convert raw git diffs into a clean commit history, analyze the working tree changes to group unrelated segments into separate commits, enforcing concise, lowercase messages without signatures or footers.

How do I group unrelated working tree changes into separate commits?▼

To group unrelated git changes into logical commits, analyze the working tree status and diffs to segment changes by module, then commit each logical group with a short, lowercase message.

Can I enforce lowercase commit messages without extraneous footers?▼

Yes, you can enforce lowercase commit messages without extraneous footers by automating the commit workflow to strip out signatures and enforce minimal, readable storytelling for module changes.

What is the best way to tell a logical story with segmented commit messages?▼

The best way to tell a logical story with segmented commit messages is to analyze git diffs across modules and group changes into stable, logical commits that enforce concise, readable histories.

Do I need to manually stage files to maintain a logical commit grouping?▼

You do not need to manually stage files to maintain logical commit grouping; the process analyzes git status and diffs to automatically segment unrelated changes into stable, logical commits.

Does automated commit grouping work with complex multi-module git diffs?▼

Yes, automated commit grouping works with complex multi-module git diffs by analyzing the raw working tree changes to target precise storytelling and maintain stable, logical commit grouping across modules.