Agent skill · software engineering · samhvw8
git-workflow
Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes.
Why this skill is useful
Provides detailed git workflows and commands for atomic commits and history management that the AI wouldn't reliably generate on its own.
What it needs
About 10k tokens when loaded. Last updated 2025-12-09. 10 stars on the source repository.
What this skill does
Git Workflow & Best Practices Purpose Comprehensive guide for git operations with emphasis on clean history, atomic commits, and professional workflows. Automatically analyzes staged changes and enforces single-responsibility principle. When to Use Activate for any git operation: Committing changes (especially multiple files) Creating branches Merging or rebasing Managing git history Writing commit messages Organizing staging area Code review preparation Repository management Core Philosophy Single Responsibility Rule ⭐ CRITICAL: Before committing, analyze staged changes and divide into atomic commits. Process: 1. Run git status to see all staged files 2. Identify different concerns/features 3. Unstage everything: git reset HEAD 4. Stage files by concern, one group at a time 5. Commit each group with focused message 6. Repeat until all changes are committed Why: Makes history reviewable, revertable, and maintainable. --- Commit Organization Analyzing Staged Changes Grouping Strategies By Feature: Auth system changes → one commit Payment module → separate commit User profile → another commit By Layer: Database migrations → first commit Backend API → second commit Frontend UI → third commit Tests → fourth commit By Type: New features (feat) Bug fixes (fix) Refactoring (refactor) Documentation (docs) Performance (perf) Tests (test) By Dependency: Foundation/infrastructure first Features that depend on foundation second Division Workflow Example: Real Scenario Situation: 29 files staged with mixed concerns Solution: Result: Clean, focused commits that are independently reviewable and revertable. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills samhvw8/git-workflow