mit einem Klick
merge-pr
// Merge a GitHub PR via squash after /preparepr. Use when asked to merge a ready PR. Do not push to main or modify code. Ensure the PR ends in MERGED state and clean up worktrees after success.
// Merge a GitHub PR via squash after /preparepr. Use when asked to merge a ready PR. Do not push to main or modify code. Ensure the PR ends in MERGED state and clean up worktrees after success.
| name | merge-pr |
| description | Merge a GitHub PR via squash after /preparepr. Use when asked to merge a ready PR. Do not push to main or modify code. Ensure the PR ends in MERGED state and clean up worktrees after success. |
Merge a prepared PR via gh pr merge --squash and clean up the worktree after success.
gh pr merge --squash as the only path to main.git push at all during merge.gh pr merge succeeds.MERGED, never CLOSED.Create a checklist of all merge steps, print it, then continue and execute the commands.
Use an isolated worktree for all merge work.
git rev-parse --show-toplevel
WORKTREE_DIR=".worktrees/pr-<PR>"
Run all commands inside the worktree directory.
Expect these files from earlier steps:
.local/review.md from /reviewpr.local/prep.md from /prepareprgh pr merge <PR> --squash --delete-branch)gh pr merge --squash only.git push at all in this command.Security scanning and remediation for AI coding agents. Scan code for vulnerabilities, generate fix patches, detect sensitive data leaks, and produce compliance reports — all from your OpenClaw agent.
Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /reviewpr. Never merge or push to main.
Review-only GitHub pull request analysis with the gh CLI. Use when asked to review a PR, provide structured feedback, or assess readiness to land. Do not merge, push, or make code changes you intend to keep.