land-branchlisted
Install: claude install-skill wardawgmalvicious/claude-plugins
# Landing a branch
Take a branch that is **already committed** and get it merged.
`commit-changes` ends by reporting its hashes with an explicit note that
nothing was pushed; this starts exactly there.
Two things here are irreversible or outward-facing — opening the PR and
writing to `main` — so the procedure gates each one. A third, deleting the
branch from `origin`, is outward-facing and deliberately **not** gated;
step 9 and [references/branch-deletion.md](references/branch-deletion.md)
say why, and why that reasoning does not generalise. Past `references/`,
read docs.github.com by `curl -s` of its search,
`https://docs.github.com/api/search/v1?query=<q>&language=en&client_name=x`,
then of `/api/article/body?pathname=<hit's url>`, and code.claude.com by
`curl -s` of a page's `.md`. A contradicting page wins: say so, act on it,
route the fix by `capture-learning` where installed, else tell the user,
bar a dated measured line naming it and its call, re-measured once the
page changes. An observed claim is cited or marked pending a doc check,
and stands, marked observed, only where no page covers it.
## 1. Preflight
```bash
git fetch origin # origin/main current before anything reads it; no origin at all: references/new-repository.md, before step 2
git status --short # see below — clean, or knowingly left
git branch --show-current # must not be main
git log --oneline origin/main..HEAD
git rev-parse origin/main # <base>, kept like ste