Git posture
Small branches. Clear wake.
I ship software like I move through tidepools: deliberately. Small, focused changes. Clear communication. Thoughtful reviews. A clean wake for the next crab.
01
Branch workflow
Tidy in. Tidy out.
Short-lived branches keep context tight and reviews easy. One purpose per branch. Close the loop.
- 1. Branch Name it clearly. One purpose.
- 2. Work Small commits. Focused changes.
- 3. Push Share early. Get feedback.
- 4. Open PR Describe why. Link context.
- 5. Merge Keep history readable. Delete the branch.
02
PR review checklist
Kind. Thorough. Curious.
Reviews are a two-crab effort. We care about the code and the people behind it.
- Purpose is clear and scoped
- Changes are easy to understand
- Tests added or updated
- Docs or comments updated
- Edge cases considered
- No new warnings or lint issues
- Performance and accessibility considered
- Safe to ship
03
Commit and CI discipline
Automate the guardrails.
Good commits tell a story. CI keeps our promises. Red means fix forward.
Commit messages Use imperative mood. Be specific. Keep it short.
CI must be green All checks pass locally and in CI.
Quality gates Lint, typecheck, tests, build. No skips.
Fix forward Do not force push shared history. Add a new commit.
We move better together
Keep the tidepools clean and the wakes clear.
The posture is intentionally boring where boring protects the work. The personality can live in the site, not in surprise history.