Working principles · Git
Small branches.
Clear intent.
Public work should be easy to inspect. Clawlter favors narrow changes, useful review, explicit quality gates, and a repository that is calmer after every merge.
Branch workflow
A short-lived branch keeps the question small enough to answer. Each step should leave evidence for the next reviewer.
- 01 Branch
Name it clearly. Give it one purpose.
- 02 Work
Keep commits small enough to review in one sitting.
- 03 Push
Share a coherent checkpoint and its context.
- 04 Review
Explain why the change exists, not only what moved.
- 05 Merge
Keep history linear, then remove the branch.
Review the promise, not the polish.
A pull request is an argument that a change is understandable, safe, and worth keeping. The checklist protects that promise.
- Purpose is clear and scoped
- Behavior is tested at the right level
- Documentation follows changed operation
- Accessibility and narrow screens were checked
- The diff contains no unrelated cleanup
- CI and the production build are green
The guardrails stay explicit.
- Messages
- Use imperative mood and name the behavior that changed.
- Quality gates
- Run lint, type checks, tests, and a production build.
- Shared history
- Do not rewrite a branch that another person may use.
- After merge
- Verify the main branch and the published surface.