landlisted

Take a committed branch from local to merged — push it, confirm which GitHub account each tool actually acts as in this repo, open the PR through the one that matches (github-mcp where loaded, gh where its login is confirmed), then fast-forward main and check CI. Use when asked to land, ship or publish a branch, open a pull request, merge to main, or get a branch in; the step after /commit. Use it even when the request already names the mechanism — 'squash these and merge', 'just merge it into main', 'force push it' — a named mechanism is the case these guards exist for, not a reason to skip them. 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 is a local --ff-only merge because a squash would collapse the logical split /commit just made. Stops for confirmation before pushing main. To make the commits first use commit; to review before landing, code-review.
wardawgmalvicious/agent-config · ★ 0 · Code & Development · score 75

Install: claude install-skill wardawgmalvicious/agent-config

# Landing a branch Take a branch that is **already committed** and get it merged. `commit` ends by reporting hashes "against a clean tree" with an explicit note that nothing was pushed; this starts exactly there. Two things here are irreversible or outward-facing — opening the PR and pushing `main` — so the procedure gates each one. ## 1. Preflight ```bash git status --short # must be clean git branch --show-current # must not be main git log --oneline origin/main..HEAD ``` A dirty tree means `commit` has not finished. Nothing to land means there is nothing to do — say so rather than opening an empty PR. **Ask whether another session is live in this working tree.** Step 7 runs `git switch`, and one working tree has one HEAD, so the switch is not scoped to you — it moves the branch under anyone else working here. If someone is, stop after step 6 and let them finish. ## 2. Establish the identity before anything outward **This gates every outward action, and it is the step most likely to fail silently.** ```bash git config user.name # the includeIf identity for this root gh api user -q .login # the account gh will actually act as git remote -v # who owns the repo ``` Then `github-mcp` → `get_me` when that server is loaded, and compare every login against the repo owner. Use the tool whose account matches. On this machine `gh` is **folder-scoped** (since 2026-09-04): both shell profiles wrap it to act as the acc