- Use short-lived branches scoped to one feature or fix
- Keep branch names descriptive and task-oriented
- Keep commits focused and logically grouped
- Write commit messages that explain intent, not just file changes
- Open PRs with clear context, scope, and verification notes
- Link related spec or ADR when applicable
- Address review feedback with follow-up commits
- Merge only after checks pass and scope is confirmed