← ClaudeAtlas

land-bundlelisted

Land two or more branches (Workflow or subagent worktrees, a fan-out of fixes, several open drafts) either as one draft pull request per slice that the `pnpm pr:land` landing train batches behind one CI run, or as one hand-built integration branch when they must be resolved together; also use when briefing a fan-out whose agents will each leave a branch. A single branch lands with `pnpm pr:land <number>` instead.
wlsdks/ontology-atlas · ★ 166 · AI & Automation · score 88
Install: claude install-skill wlsdks/ontology-atlas
# Land many branches `pnpm pr:land` is a queue now: it labels the pull request `landing-queue`, and the conductor merges up to 20 queued pull requests onto one `train/*` branch behind **one** CI run, bisecting a red train so one bad slice is ejected instead of blocking the rest. So twenty independent slices no longer need a hand-made bundle to share a CI run. The bundle remains for branches that only make sense resolved together. ## 0. Before the fan-out (when you author the Workflow or brief) - Each agent works in its own worktree, commits on its own branch, and runs `pnpm checks:changed -- --run` for its slice. Whether it pushes and opens its own draft is the brief's call: yes for the train path, no for a bundle. - Name the branches with one prefix you can select later, such as `wf/<topic>/<slice>`, or keep the worktrees under one directory. - Give ratchet baselines, a shared message namespace file and shared docs one owner, or expect to recount them on the merged tree (`/parallel-brief` §2). ## 1. Select, plan, and choose the path ```bash pnpm bundle:plan -- --match='wf/<topic>/*' # or branch names, or --worktrees=<dir> ``` The plan (no ref, index or worktree changes) reports each branch as `empty`, `contained` (already in `origin/main`) or `pending`, lists files that two branches both touch, and trial-merges the pending ones in the order given. Leave `empty` and `contained` branches out. Selection is always explicit. Never sweep branches you did not