amadan
docs: prefer small, focused, incrementally-shippable PRs (#200)
Add guidance to the Branches, commits & PRs section: when iterating, slice work into the smallest change that stands on its own and land it, rather than batching a large feature into one big PR.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 file changed,
+5
−0
CLAUDE.md+5 −0
diff --git a/CLAUDE.md b/CLAUDE.md| index 6d6e5a1..66af338 100644 |
| --- a/CLAUDE.md |
| +++ b/CLAUDE.md |
| @@ -218,6 +218,11 @@ Principles that hold regardless of environment: |
| ## Branches, commits & PRs |
| +- **Prefer small, focused PRs that ship incrementally.** When iterating, slice |
| + work into the smallest change that stands on its own and land it, rather than |
| + batching a large feature into one big PR. Small PRs review faster, merge with |
| + fewer conflicts (several land in parallel), and are safer to deploy and revert. |
| + Split a big idea into a sequence of shippable steps. |
| - **Work on a feature branch — don't commit straight to `main`.** Several PRs |
| land in parallel, so pushing directly to `main` causes push races and forced |
| rebases. Branch per feature (e.g. `reply-to-messages`), open a PR, and |