git-workflow

One consistent, opinionated git workflow that scales from a solo weekend project to a multi-person, multi-month repo — so you (and your agents) stop improvising commit messages, branch names, and release habits per project. The defaults here favor a clean, linear, reviewable history.

Surfaces, separated by the question they answer:

Surface	Question it answers
`references/project-tiers.md`	"Do I commit to `main`, use a `dev` branch, or open PRs?"
`references/conventional-commits.md`	"What exactly goes in the commit message, including AI provenance?"
`references/worktrees-parallel-agents.md`	"How do I run parallel agents without collisions?"
`references/versioning-and-releases.md`	"When and how do I tag a version?"
`references/branch-hygiene.md`	"Which local branches are done vs still in-dev?"
`scripts/branch-status.sh`	Same, as data — classify every local branch.
`scripts/check-commit-msg.sh`	"Is this commit message valid?"
`references/lazygit-cheatsheet.md`	"How do I do this in lazygit?" (learning aid)