integration-by-batcheslisted
Install: claude install-skill RonenMars/threadbase-mobile
# Integration by batches (shared core)
`integration-branch` merges *every* PR into one branch. When QA finds a defect in that branch you cannot say which PR caused it. This skill cuts the open PRs into **batches of related PRs**, QAs each batch alone, and lands it before the next one starts.
Reuse `integration-branch` for the mechanics it already proves (worktree, push guard, per-PR rebase + `merge --no-ff`, sweeps, cleanup). This file states what differs.
Each repo's own `integration-by-batches` skill holds its QA targets, build and gate commands, and landing differences. Read it too. Where it is stricter than this file, follow it.
## Hard rules
1. **Nothing merges to `main` before that batch's explicit QA approval.** Not a green CI, not a quiet user.
2. **One batch at a time.** Do not build, deploy or merge batch N+1 until batch N is approved *and* landed.
3. **Never combine unrelated PRs to lower the batch count.** A batch is a unit of attribution.
4. **Never decide a product question silently.** Conflicts that are an either/or about behaviour (J-calls) stop the run and are put to the user with the options.
5. **The integration *branch* never reaches `origin`.** Push nothing unless QA needs an origin ref, and then only an annotated **test tag**, never the branch. Prove it before every report: `git ls-remote --heads origin "integration/*" | wc -l` → `0`.
6. **Never commit the plan or the log.** They are working notes. Keep them outside any repo.
7. **Preserve each PR's