git-workflow

Analyze staged Git changes and split them into atomic commits.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/brixtonpham/claude-setup --skill git-workflow-brixtonpham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/brixtonpham/claude-setup/tree/main/hub/skills/git-workflow
Command: npx skills add https://github.com/brixtonpham/claude-setup --skill git-workflow-brixtonpham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows often produce monolithic commits that intertwine multiple concerns. This Skill analyzes staged changes and guides you to split them into atomic commits, preserving clear history and easier reversions.

Core Features & Use Cases

  • Analyze Staged Changes: Inspect what is about to be committed and categorize by concern.
  • Atomic Commit Guidance: Split changes into independent commits with focused messages.
  • Gate Before Commit: Detect multi-concern commits and prompt user to separate them before committing.
  • Use Case: When preparing a large feature, run this skill to craft a sequence of focused commits for each subtask, enabling clean PR reviews.

Quick Start

Analyze my current staged changes and propose atomic commits with concise messages, then apply the first commit.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I split staged git changes into atomic commits?

Atomic commits isolate a single concern per commit, making history cleaner and reversions easier. This skill analyzes staged changes by running git status and diff, then guides you to split them into independent commits with focused conventional-commit-like messages.

How do I write conventional commit messages for multi-file changes?

This skill analyzes staged multi-file changes, splits them by concern, and produces focused conventional-commit-like messages for each independent commit. You get clear history and easier reversions when preparing features, fixes, or refactors.

What is the best way to clean up git history before a pull request?

The best way to clean up git history before a pull request is to split monolithic commits. This skill detects multi-concern staged changes, prompts you to separate them, and generates focused conventional-commit-like messages for cleaner PR reviews.

Can I use this skill for branching and refactoring workflows?

Yes, you can use this skill for branching and refactoring workflows. It applies atomic commit analysis during commit preparation, branching, and history cleanup across features, fixes, and refactors without requiring external dependencies.

Why does my git commit contain multiple unrelated changes?

Your git commit contains multiple unrelated changes when staged files intertwine features, fixes, and refactors. This skill analyzes your staged diff, detects multi-concern commits, and prompts you to separate them into atomic commits before committing.