# Git Flow Pro > Handle git hygiene — write commit messages that explain the why, name branches that match the issue, draft PR descriptions reviewers actually read. Knows Conventional Commits, semantic branch names, and how to break a noisy WIP into clean atomic commits. Use when the user says "commit this", "make a PR", "write the commit message", "draft a PR description", "clean up my branch", "rebase this", or finishes work and wants it shipped. - Skill: `ak-ship/git-flow-pro` (Agent Skill) - Install (CLI): `npx skillmds@latest add ak-ship/git-flow-pro` - Raw SKILL.md: https://api.skillmd.com/api/skills/ak-ship/git-flow-pro/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: ak-ship (https://skillmd.com/u/ak-ship) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/ak-ship/git-flow-pro --- # git-flow-pro — small, clear commits; PRs that get reviewed ## When to use this skill Trigger when the user wants to package work for review or history. Strong signals: - "commit this", "make a commit", "git commit" - "open a PR", "draft a PR description" - "clean up my branch", "squash these", "rebase onto main" - "what should I name this branch?" Do *not* trigger for: pushing to main (require confirmation), force-pushing to shared branches (require confirmation), or rewriting published history (require confirmation). ## The output contract Git artifacts that: 1. **Tell a story** — the commit log reads like a changelog. Each commit is one logical change. 2. **Match conventions** — Conventional Commits (or whatever the repo uses), the team's branch naming, the team's PR template. 3. **Explain the *why*** — not the diff. The diff already shows what changed. 4. **Stay safe** — no force-push to shared branches without explicit confirmation; no rewriting commits that have been reviewed. ## Workflow ### 1 — Sense the conventions Before writing anything: - `git log --oneline -20` — what does this project's history look like? Conventional Commits (`feat:`, `fix:`)? Imperative present tense? Past tense? - `cat .github/pull_request_template.md 2>/dev/null` — is there a PR template? - `git branch -r --contains HEAD | head` — what's the trunk branch called (`main`, `master`, `trunk`, `develop`)? - `git config user.email` and the recent author list — match the style of the current contributors. Mirror what's there. Don't introduce Conventional Commits to a project that uses prose, and vice versa. ### 2 — Stage with intent Read `git status` and `git diff --cached` (and unstaged). Group changes by intent: - One feature → one commit - A test for that feature → squashed into the same commit, or right after - An unrelated typo fix you noticed → separate commit - Generated files (`package-lock.json`, etc.) → include if they belong to the same change Use `git add -p` mentally — pick hunks per commit, not whole files when the file has mixed concerns. ### 3 — Write the commit message Format (when Conventional Commits is in use): ``` ():