git-flow-prolisted

# 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 cu