plugins/ls-git/skills/merge-pull-request/SKILL.md
Use when merging a single GitHub pull request. Handles pre-flight checks, waits for CI, and executes the merge with the repo's default method or merge queue.
npx skillsauth add LandonSchropp/agent-toolkit plugins/ls-git/skills/merge-pull-requestInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pass --pull-request-url <url> to each script. Use a 5-minute tool timeout when running the polling scripts. If a script times out, check for any issues, then re-run it — repeat up to 5 times before giving up.
Wait until ready: Run scripts/wait-for-pull-request-to-be-ready.sh. Waits for CI to complete and verifies all static conditions (not draft, no conflicts, reviews approved). Exits immediately on any permanent blocker — stop and surface the error to the user.
Merge: Run scripts/merge-pull-request.sh. Detects whether the target branch uses a merge queue — if so, adds the pull request to the queue without a strategy flag. Otherwise detects the repo's allowed methods (squash > merge commit > rebase) and merges with --delete-branch.
Confirm: Run scripts/wait-for-pull-request-to-be-merged.sh. Polls until the pull request state is MERGED. Required when a merge queue is involved since the merge completes asynchronously.
| Thought | Reality |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| "CI is almost done, I'll skip wait-for-pull-request-to-be-ready" | Use the script. It handles the wait. |
| "The pull request is blocked on approvals, I'll use --admin" | Admin bypass is a user decision, not the skill's. Surface the block and stop. |
tools
Use when working with a stack of GitHub pull requests — creating branches, keeping the stack in sync, or merging in order. Covers Git Town setup, PR targeting, rebasing, and landing the stack.
tools
Use when writing or modifying tests in a Bun project
tools
Use when publishing or releasing a new version of an npm/pnpm/yarn/bun package to the registry. Covers package-manager detection, semver bump selection, tagging, pushing, scoped-package access, authentication, and one-time passwords (OTP).
tools
Use when a finished worktree's branch has been reviewed and committed and needs to land. Rebases onto the latest default branch, then either fast-forwards it into the default branch (personal direct-to-main repos) or pushes it for a pull request (shared feature-branch repos).