smart-commit

Group unstaged Git changes into atomic commits with conventional messages.

19|4|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/wunki/amplify --skill smart-commit-wunki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-commit
Source: https://github.com/wunki/amplify/tree/main/skills/smart-commit
Command: npx skills add https://github.com/wunki/amplify --skill smart-commit-wunki

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps organize messy, unstaged code changes into clean, logical, and atomic commits, making your Git history much easier to understand and manage.

Core Features & Use Cases

  • Automatic Grouping: Analyzes unstaged changes and groups them by logical purpose, scope, and dependencies.
  • Conventional Commits: Generates well-formatted commit messages following the conventional commit standard.
  • User Confirmation: Presents a proposed commit plan for review and approval before executing any commits.
  • Use Case: After a long coding session with many unrelated changes, use this Skill to split them into individual, meaningful commits like feat: add user login, fix: correct validation error, and chore: update dependencies.

Quick Start

Use the smart-commit skill to group my unstaged changes into atomic commits.

Frequently Asked Questions about smart-commit

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

FAQPage Schema
How do I group unstaged git changes into atomic commits?

Splitting unstaged changes into atomic commits involves analyzing file diffs, grouping related modifications by single responsibility, and generating conventional commit messages before staging and committing each logical unit.

What is an atomic commit in version control?

An atomic commit in version control is a single, self-contained change that addresses one specific feature or fix, ensuring the repository history remains coherent, easy to review, and simple to revert if necessary.

How do I automatically generate conventional commit messages for my code changes?

You can generate conventional commit messages by analyzing unstaged Git changes, grouping them by logical purpose and scope, and producing formatted messages like feat or fix for user confirmation before execution.

Can I review the commit plan before executing atomic commits?

Yes, you can review the commit plan before execution. The system presents a proposed grouping of unstaged changes and conventional commit messages for your confirmation, ensuring safe and organized version control.

How do I split a messy working directory into logical git commits?

Split a messy working directory by analyzing unstaged Git changes, grouping them by logical purpose and dependencies, and creating separate atomic commits with conventional messages for organized version control.

Does smart-commit work without any external dependencies?

Yes, smart-commit operates without external dependencies. It uses internal scripts and references to analyze unstaged Git changes, group them into atomic commits, and generate conventional commit messages for user confirmation.