← ClaudeAtlas

land-branchlisted

Takes a committed branch from local to merged — pushes it, confirms which GitHub account each tool actually acts as in this repo, opens the PR through the one that matches (gh where its login is confirmed, else github-mcp where loaded), then integrates it into main, reports CI, and deletes the merged branch locally and on origin. Guards two silent failures: gh and github-mcp can authenticate as different accounts, so a PR lands under the wrong identity with no error, and integration preserves every SHA — a local --ff-only merge by default, a no-checkout refspec push where another session holds the tree, or a server-side merge commit where main requires a pull request — because a squash would collapse the logical split commit-changes just made. Stops for confirmation before the write to main. To make the commits first use commit-changes; to review before landing, review-code, or the bundled /code-review where review-code is absent.
wardawgmalvicious/claude-plugins · ★ 0 · Code & Development · score 78
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