git-patternslisted

# Git Patterns Review checklist and the handful of git behaviors that are easy to get wrong. Command syntax is in the man pages; this file is what to flag and what to reach for. ## Conventional Commits ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` - `feat` bumps MINOR, `fix` bumps PATCH, everything else (`docs`, `style`, `refactor`, `perf`, `test`, `chore`, `ci`) bumps nothing. - Breaking change: `!` after the type/scope, or a `BREAKING CHANGE:` footer. Either maps to MAJOR. - Match the project's existing style before assuming Conventional Commits - see `rules/workflow.md`. Branch naming for this machine is `<type>/<slug>` or `<type>/<TICKET-ID>/<slug>`, generated by `branch_name.sh`; the type vocabulary lives in the root `CLAUDE.md`. --- ## Reach for these | Situation | Tool | | ---------------------------------------- | ------------------------------------------------------------------------ | | Commits lost after a bad rebase or reset | `git reflog` - every HEAD move is recorded; branch off `HEAD@{n}` | | Need each commit in a series to build | `exec` lines in the `rebase -i` todo (`exec make test`) | | Hunting the commit that broke something | `git bisect run <cmd>` - automates the whole search; exit 0 = good | | Reviewing a branch mid-edit on another | `git worktree add <dir> <branch>` - sepa