auto-commits

Analyze git changes and propose atomic Conventional Commit plans for user approval.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/wwsun/skills --skill auto-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-commits
Source: https://github.com/wwsun/skills/tree/main/skills/auto-commits
Command: npx skills add https://github.com/wwsun/skills --skill auto-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of creating clean, logical, and atomic git commits when making multiple changes across modules or features, ensuring better version control and review clarity.

Core Features & Use Cases

  • Grouping Changes: Analyzes git status and diff outputs to organize modified files into meaningful groups based on modules, features, or logic.
  • Proposing Commit Plan: Generates a structured plan using Conventional Commits to clearly describe each commit's scope and purpose.
  • User Confirmation: Waits for user approval before executing staged commits, preventing unintended changes.
  • Sequential Execution: Automates the process of staging files and creating commits according to the approved plan, enhancing workflow efficiency.

Quick Start

Use the auto-commits skill to analyze recent changes, plan structured commits, and get your approval before applying them to the repository.

Frequently Asked Questions about auto-commits

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

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

The auto-commits process analyzes git status and diff outputs to organize modified files into logical groups, proposes a structured plan with Conventional Commit messages, and executes sequentially after user approval.

What is the best way to automate Conventional Commits for multiple modules?

Automating Conventional Commits involves generating a structured plan that describes each commit's scope and purpose, automating staging, and creating commits sequentially based on user-approved groupings.

How do I ensure code review clarity when committing multiple feature changes?

You ensure review clarity by creating clean, logical, and atomic git commits that group modified files based on modules or features, preventing unintended changes through a user confirmation step before execution.

Can I review and approve a structured git commit plan before it is executed?

Yes, this workflow seeks user confirmation by waiting for approval before executing staged commits, ensuring you maintain control over the version control process and preventing unintended changes.

Does this automated commit workflow work without external dependencies?

Yes, this workflow operates without external dependencies, relying solely on scripts and references to analyze git status, propose structured plans, and stage files sequentially within your current version control setup.