skills.rest
Takfes
TakfesCOMMUNITY
Explore all skills by this author →
GitHub

git-commit-wizard

Group uncommitted Git changes into atomic commits with Conventional Commits messages.

Updated May 6, 2026
Search Tags:#git#commits#code-review#atomic-commits#version-control#conventional-commits
One-click install
npx skills add https://github.com/Takfes/indie-scaffolder --skill git-commit-wizard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-wizard
Source: https://github.com/Takfes/indie-scaffolder/tree/main/components/agent-skills-commands/.agents/skills/git-commit-wizard
Command: npx skills add https://github.com/Takfes/indie-scaffolder --skill git-commit-wizard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps when a work session leaves you with many mixed changes and you need to turn them into a clean, reviewable commit history instead of a single cluttered commit.

Core Features & Use Cases

  • Groups related files by feature, fix, docs, tests, or infrastructure so each commit has a single purpose.
  • Proposes atomic commit batches, including files that should stay together, like source code with its tests.
  • Drafts Conventional Commits messages with a concise subject, a useful body, and optional footers for issues or co-author credit.
  • Use it after refactors, multi-feature sessions, or pre-push cleanup when the repository has scattered changes across several paths.

Quick Start

Use the git-commit-wizard skill to inspect my current Git changes, propose logical commit groups, and draft Conventional Commit messages for each group.

Frequently Asked Questions about git-commit-wizard

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

FAQPage Schema
How do I organize multiple uncommitted Git changes into clean atomic commits?▼

To organize uncommitted Git changes into atomic commits, the Skill analyzes your working directory, groups related files by purpose like features or fixes, and proposes logical commit batches for your review before staging.

How do I write Conventional Commits messages for mixed feature and fix work?▼

Writing Conventional Commits messages for mixed work involves grouping related file changes into atomic batches, then drafting a concise subject, a useful body, and optional footers for issues or co-author credit.

Can I group scattered Git changes by feature before a pre-push cleanup?▼

Yes, you can group scattered Git changes before a pre-push cleanup by analyzing file modifications across several paths and clustering them into logical batches based on their purpose.

Does the git-commit-wizard Skill keep source code and tests in the same commit?▼

Yes, the git-commit-wizard Skill keeps source code and its corresponding tests in the same commit by proposing atomic commit batches that logically group related files together for a single purpose.

What is the best way to split a messy refactoring session into reviewable version control history?▼

The best way to split a messy refactoring session into reviewable version control history is to analyze the changes, group them into single-purpose atomic commits, and apply Conventional Commits formatting.

Related Skills

Explore More Software Engineering Skills→
23prime23prime

reviewing-changes

Review uncommitted Git working tree changes for bugs and errors.

Community
Intermediate
iludeilude
8

git-workflow

Validate Git commits for secrets and enforce safe push rules.

Community
Intermediate
guille-galloguille-gallo

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged for Git repositories.

Community
Intermediate
joegoldinjoegoldin
2

git-hunk

Stage, unstage, and inspect Git hunks by hash non-interactively.

Community
Intermediate