auto-merge

Catalogue repository state and merge pull requests that pass all readiness gates.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill auto-merge-diy-accounting-uk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-merge
Source: https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk/tree/main/.claude/skills/auto-merge
Command: npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill auto-merge-diy-accounting-uk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Merging pull requests without checking review state, workflow results, uncommitted work, and in-flight deploys leads to lost commits, broken deploys, and irreversible mistakes. This Skill enforces a single gated path for merging so nothing ships that has not passed every check. ## Core Features & Use Cases - Full repository inventory: Catalogues worktrees, branches, uncommitted changes, open PRs, review threads, and workflow runs into a single state table before any action. - Gated merge eligibility: Blocks merges on drafts, unresolved review threads, CHANGES_REQUESTED reviews, conflicting branches, unpushed commits, and failed or missing workflow runs. - Sequential verified merges: Merges one PR at a time, waits for each merge to land, verifies it via the GitHub API, and rebases remaining PRs only when needed. - Use Case: An operator says "merge what's ready" and the Skill renders the full repository state, merges only the PRs that pass every gate, and hands off to a post-merge watch for the resulting deploy. ## Quick Start Ask the assistant to run auto-merge and show the merge state of the repository.

Frequently Asked Questions about auto-merge

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

FAQPage Schema
How do I safely merge multiple GitHub pull requests at once?▼

Merge one PR at a time and wait for each merge to land before starting the next, since simultaneous merges trigger competing deploys. Verify each merge through the GitHub API and check that no commits were left behind on the branch.

What checks should pass before merging a pull request?▼

Confirm the PR is not a draft, has no CHANGES_REQUESTED reviews or unresolved review threads, has no merge conflicts, and that the latest run of every workflow against its head SHA succeeded. Also verify the branch is not ahead of origin and has no uncommitted work in a worktree.

Why does a cancelled GitHub Actions run block a merge?▼

A cancelled run is usually superseded by a newer run of the same workflow on the same SHA. If a later run succeeded, the cancellation is noise; if none exists, the workflow never produced evidence and the merge must wait.

Can I merge a PR when its checks show no workflow runs?▼

No. An empty run list means no data, not a pass, since runs take time to register after a push. A head SHA with zero runs is too early to judge and must not be treated as green.

When should I rebase open PRs after merging one?▼

Rebase only when the remaining PR conflicts with main or its changed files overlap the merged PR's files. Push the rebase with force-with-lease only when no deploy is in flight on that branch, and never resolve conflicts automatically.