commit

Analyze unstaged changes and suggest atomic commit groups with messages

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 29, 2025⬇️2downloads

When & Why to Use This Skill

This Claude skill streamlines the version control workflow by analyzing unstaged Git changes and organizing them into logical, atomic commit groups. It enhances repository maintainability by automatically generating descriptive commit messages and suggesting a structured staging plan, ensuring a clean and readable project history for development teams.

Use Cases

  • Atomic Commit Management: Automatically split a large, complex diff containing multiple bug fixes and feature updates into separate, logical commits to maintain a clean Git history.
  • Automated Documentation: Generate precise and meaningful commit messages based on actual code changes, reducing the cognitive load on developers and improving team communication.
  • Workflow Optimization: Speed up the local development cycle by automating the repetitive tasks of analyzing, grouping, and staging files before pushing to a remote repository.
  • Code Organization: Identify dependencies between changed files to ensure that commits are made in the correct order, preventing broken builds in the version history.
namecommit
descriptionAnalyze unstaged changes and suggest atomic commit groups with messages

Current Time: !date

I need to make small, logical, atomic commits based on my current work.

Optional focus argument: "frontend only", "exclude tests"

Here is the current status of the repository: !git status

Here are the specific unstaged changes (diff): !git diff

Please analyze these changes and suggest a plan to stage and commit them in a logical order.

  1. Group the changes into atomic units (e.g., by feature, fix, or refactor).
  2. For each group, list the specific files (or hunks, if applicable) to stage.
  3. Provide a commit message for each group.
  4. If there are dependencies (e.g., File A must be committed before File B), please note them.
  5. Unless there any questions proceed with creating the commits
  6. DO NOT PUSH UNDER ANY CIRCUMSTANCE

$ARGUMENTS