auto-merge-dry-run

Reports what pull requests would merge without performing any merge, commit, or push.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before letting an automated merge process touch your repository, you need to know exactly what it would do. This Skill runs the full auto-merge analysis—gathering PR data, rendering status tables, and reaching merge verdicts—while taking no action whatsoever, so you can inspect the outcome risk-free. ## Core Features & Use Cases - Full dry-run reporting: Produces the same catalogue, tables, and verdicts as the live auto-merge run, clearly labeled as a dry run. - Actionable command output: Prints the exact commands the live run would have executed in fenced blocks prefixed with !, so you can run any step by hand. - Blocking-gate visibility: When nothing is ready to merge, reports the blocking gate for every PR instead of failing silently. - Use Case: Before enabling automated merging on a busy repository, run this Skill to confirm which PRs would merge, which are blocked, and why—then invoke the live auto-merge only when satisfied. ## Quick Start Ask the assistant to run a dry run of auto-merge to show which pull requests would merge and what commands it would execute, without changing anything.

Frequently Asked Questions about auto-merge-dry-run

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

FAQPage Schema
How do I preview which pull requests would auto-merge before merging?▼

Run the auto-merge dry-run to gather all PR data, render the full status tables, and reach merge verdicts without taking action. Rows that qualify are marked as 'would merge', and the exact commands the live run would execute are printed for manual use.

What is the difference between auto-merge and auto-merge dry run?▼

The dry run follows the same auto-merge logic and produces identical tables and verdicts, but performs no merge, commit, push, rebase, branch deletion, file writes, or PR comments. It exists purely to show what the live run would do.

Does a dry run change any files or branches in the repository?▼

No. The dry run takes no action: no merge, no commit, no push, no rebase, no branch or worktree deletion, no writes to tracked files, and no PR comments or labels. It only reads state and reports.

What happens when a dry run finds no pull requests ready to merge?▼

A dry run that finds nothing ready is treated as a useful result, not a failure. The run reports the blocking gate for every PR and stops, giving you a clear picture of repository state before changing anything.

How do I execute the merges after reviewing a dry run?▼

Either invoke the live auto-merge command to perform the merges automatically, or copy individual commands from the dry run's fenced output blocks, which are prefixed with `!` so you can run any of them by hand.