git-workflow

Enforce atomic commits and conventional-commit messages in git workflows.

Updated Dec 23, 2025

Search Tags:#git #workflow #branching #code-review #pull-request #conventional-commits #atomic-commit

Ready to run

npx skills add https://github.com/dige04/hieu-ccsetup --skill git-workflow-dige04

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/dige04/hieu-ccsetup/tree/main/config/skills/git-workflow
Command: npx skills add https://github.com/dige04/hieu-ccsetup --skill git-workflow-dige04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative software projects often accumulate non-atomic, multi-file commits, causing messy history and difficult code reviews. This skill provides a principled workflow to analyze staged changes, split them into atomic commits, and manage branches, merges, and PRs with conventional-commit practices.

Core Features & Use Cases

Enforce single-responsibility commits by analyzing staged changes and batching related files into atomic commits.
Guide branching strategies, merge/rebase workflows, and PR hygiene to maintain a clean project history.
Use case: when preparing a feature for review across multiple files, the tool ensures each commit represents a single concern and is ready for code review.

Quick Start

Describe the staged changes in your repo and I will organize them into atomic commits following single-responsibility rules.

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 changes into atomic commits?▼

This tool analyzes your staged changes and groups related files into atomic commits, ensuring each commit represents a single concern for easier code review and clean history.

What is an atomic commit and when do I need it in git?▼

An atomic commit is a single-responsibility commit that groups only related changes. You need it in collaborative software projects to maintain a clean history, simplify code reviews, and prevent multi-file commits from obscuring changes.

How do I enforce conventional commit messages in a pull request workflow?▼

You can enforce conventional commit messages in a pull request workflow by applying a principled gate that validates commit formats, guides branching strategies, and manages merge or rebase procedures before review.

What is the best way to manage branching and rebasing for a clean git history?▼

The best way to manage branching and rebasing for a clean git history is to use an automated workflow that guides merge and rebase procedures while enforcing single-responsibility commits and conventional-commit practices.

Can I use this git workflow tool for team-based collaborative development?▼

Yes, this workflow is designed for team-based collaborative development, enforcing pull-request hygiene, branching strategies, and atomic commits across multiple files to maintain clean project history.

Why does my git history get messy with multi-file commits?▼

Your git history gets messy because non-atomic multi-file commits mix unrelated concerns. Splitting staged changes into single-responsibility atomic commits resolves this by ensuring each commit represents a single concern.