Enforce atomic commits and conventional-commit messages in git workflows.
npx skills add https://github.com/dige04/hieu-ccsetup --skill git-workflow-dige04
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
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.
Describe the staged changes in your repo and I will organize them into atomic commits following single-responsibility rules.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
jeremylongshoreGenerate conventional commit messages from staged Git changes.
tachiiri-orgCreate a pull request from the dev branch to main after verifying branch and remote state.
robertbr123Automate code review with security scans, quality checks, and automated fixes.
UtsavBalar1231Stage Git changes at file, hunk, or line-range granularity using the pgs CLI.
