Does this skill follow Conventional Commits standards?

Yes, it uses standard types like feat, fix, refactor, chore, docs, and style, ensuring your repository history remains professional and compatible with automated changelog tools.

Does it commit my code automatically without review?

No. Smart Commit always presents a proposed plan first. You must explicitly confirm the plan, and you have the option to skip specific commits or edit the groupings before anything is executed.

How does Smart Commit decide which files belong together?

The skill analyzes the purpose, scope, and relationships of changed files. It follows grouping rules such as keeping components with their tests/styles and separating configuration changes into 'chore' commits.

What happens if I have merge conflicts?

If merge conflict markers are detected, Smart Commit will stop and prompt you to resolve the conflicts manually before it can safely organize your changes.

Smart Commit

Name: Smart Commit
Author: wunki

bywunki

•

개발자 도구

Organizes uncommitted changes into logically grouped, atomic Git commits with professional conventional messages.

Smart Commit streamlines the development workflow by intelligently analyzing a working directory's uncommitted changes and grouping them into logical, atomic units. It identifies related files—such as a component and its corresponding tests or styles—and suggests a sequenced commit plan using the Conventional Commits standard. This skill is ideal for developers who have accumulated multiple distinct changes across different modules and want to maintain a clean, readable project history without the tedious manual staging of individual files.

주요 기능

0117 GitHub stars

02Intelligent grouping of related changes into atomic, single-responsibility commits

03Comprehensive analysis of staged, unstaged, and untracked files

04Interactive commit planning with options to proceed, skip, or edit groupings

05User-facing commit bodies that focus on impact rather than implementation details

06Automatic generation of Conventional Commit messages (feat, fix, refactor, etc.)

사용 사례

01Splitting a large feature implementation into smaller, more reviewable commits

02Cleaning up a workspace with many diverse changes before pushing a PR

03Standardizing commit history format across a team using Conventional Commits

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add wunki/amplify smart-commit

For use in Claude.ai and ChatGPT

Download Skill