auto-merge-rearms-while-agent-live-kill-then-disarm-verify

Holds GitHub pull requests by killing the agent, disarming auto-merge, and verifying state.

3|Updated May 8, 2026
One-click install
npx skills add https://github.com/wan-huiyan/agent-traffic-control --skill auto-merge-rearms-while-agent-live-kill-then-disarm-verify-wan-huiyan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-merge-rearms-while-agent-live-kill-then-disarm-verify
Source: https://github.com/wan-huiyan/agent-traffic-control/tree/main/plugins/agent-traffic-control/skills/auto-merge-rearms-while-agent-live-kill-then-disarm-verify
Command: npx skills add https://github.com/wan-huiyan/agent-traffic-control --skill auto-merge-rearms-while-agent-live-kill-then-disarm-verify-wan-huiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Disarming auto-merge on a pull request whose agent is still running does not hold it — the agent re-arms auto-merge within minutes and the PR merges anyway, because arming is a step in the agent's brief and your disarm was never addressed to the agent. This Skill provides the correct procedure to actually stop a PR from merging. ## Core Features & Use Cases - Ordered hold procedure: Kill the agent first, then run gh pr merge --disable-auto, then verify by reading autoMergeRequest back — and re-check minutes later, since re-arming is the failure mode. - Strong draft-based hold: Convert the PR to a draft with gh pr ready --undo, which GitHub enforces at the platform level so no agent can merge it regardless of ordering. - Enforced hold lists: Publish hold lists that name what actually stops each PR (draft, disarmed with stopped agent, or announced-only) instead of relying on agents reading instructions. - Use Case: You disarmed auto-merge on PR #123 for review, but it merged minutes later because its agent was still live. Use this Skill to stop the agent, disarm, verify the state twice, or convert the PR to a draft so the hold cannot be overridden. ## Quick Start Hold pull request 123 by converting it to a draft with gh pr ready --undo, then verify with gh pr view that isDraft is true and autoMergeRequest is null.

Frequently Asked Questions about auto-merge-rearms-while-agent-live-kill-then-disarm-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop a GitHub pull request from auto-merging?▼

Stop the agent that armed it first, then run gh pr merge --disable-auto, then verify by reading autoMergeRequest back with gh pr view. The strongest option is gh pr ready --undo, which converts the PR to a draft that GitHub refuses to merge.

Why does auto-merge re-enable itself after I disable it?▼

The agent that opened the PR is still running and arming auto-merge is a step in its brief, so it re-arms the PR on a later step. Disarming changes the state but not the intent of the process that keeps re-asserting it.

Does converting a pull request to a draft prevent merging?▼

Yes, GitHub refuses to merge draft pull requests with a 'Pull Request is still a draft' error, regardless of auto-merge state or agent actions. Use gh pr ready --undo to convert, and gh pr ready to mark it ready again later.

Can deleting a branch hold a pull request?▼

No, deleting the head branch closes the PR and loses the review thread context. Recovery requires restoring the branch from refs/pull/<N>/head and reopening. Cleanup routines should only delete branches when mergedAt is not null.

How do I verify a pull request hold actually worked?▼

Confirm the agent is stopped, then check gh pr view --json autoMergeRequest returns null or isDraft is true. Repeat the same read at least five minutes later, since re-arming takes minutes and an immediate check cannot see it.