A command that watches a GitHub pull request's automated checks, merges it after all checks pass, and updates the local branch.

Monitoring a pull request by number or URL, choosing squash or regular merge, merging only after successful checks, and bringing the merged changes into the local branch.

It avoids repeatedly checking whether continuous integration, or automated code tests and checks, has finished. It stops when checks fail and asks which merge method to use.

await-merge — Command for coding agents by bengous: A command that watches a GitHub pull request's automated…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/bengous/claude-code-plugins/await-merge

Clone the repo

git clone --depth 1 https://github.com/bengous/claude-code-plugins

Or install git-tools, the plugin that ships this one along with the rest of its 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/bengous/claude-code-plugins/await-merge.svg)](https://agentmods.dev/commands/bengous/claude-code-plugins/await-merge)

Your own site

<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/await-merge"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/await-merge.svg" alt="Measured on agentmods" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 420 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00420
Opus 5	$0.00006	$0.00210
Sonnet 5	$0.00003	$0.00084
Haiku 4.5	$0.00001	$0.00042

Measured 3d ago against content hash 9b9bebfa1ed3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

await-merge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

git-tools/commands/await-merge.md · 64 lines

What it actually says

Monitor CI checks on a PR. When all checks pass, merge the PR and update the local branch to include the merged changes.

PR Detection

Use $ARGUMENTS if provided (PR number or URL). Otherwise, detect from current branch with gh pr view. If detection fails, stop and ask the user to provide the PR number.

Workflow

1. Gather PR info

Run these commands to gather context:

gh pr view <pr> --json number,baseRefName,commits,title
gh pr checks <pr>

2. Ask merge strategy

Use AskUserQuestion to let the user choose:

Question: "How should this PR be merged?" Header: "Merge" Options:

Squash - Combine all commits into one
Merge - Keep individual commits

Include the commit count and titles in the question context so the user can make an informed decision.

3. Monitor CI

Poll gh pr checks until all checks complete. Report status changes as they occur.

If checks fail: Stop and report which checks failed. Do not attempt to merge.

4. Merge

When all checks pass, merge the PR using the strategy chosen in step 2.

Execute: gh pr merge <pr> --delete-branch with --squash or --merge accordingly.

If merge fails: Report the error (conflicts, branch protection, etc). Do not retry.

5. Update local

Checkout the base branch and pull:

git checkout <baseRefName>
git pull

6. Report outcome

Summarize: PR merged, strategy used, local branch updated.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 64 lines · 13 tokens per session scan A 9b9bebfa1ed3

Subscribe to this mod's changes

await-merge is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 420 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

CI and CD DevOps and cloud Git and workflow Releases automation claude-code developer-tools workflow

await-merge