ad-merge

Evaluate and merge GitHub pull requests with automated preflight checks and merge strategy detection.

728|16|Updated Mar 9, 2026

Search Tags:#automation #github #reviews #gh-cli #ci-checks #pr-merge

Ready to run

npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-merge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ad-merge
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-merge
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates and merges GitHub pull requests with automated preflight checks, evaluation of CI and reviews, and an auto-detected merge strategy. This process helps teams land PRs safely by enforcing CI results, review outcomes, and a consistent merge method.

Core Features & Use Cases

End-to-end PR automation: preflight checks, CI status evaluation, review gating, and automatic merge mode detection.
Flexible merge strategies: automatically chooses from squash, rebase, or merge commits with an optional delete-branch step for feature branches.
Triggered guidance: responds to commands like "merge this PR", "evaluate the PR", "is it mergeable", or "gh pr merge" to orchestrate the workflow.

Quick Start

Provide a PR URL or branch and the assistant will guide you through preflight checks, evaluation, and a safe merge.

Frequently Asked Questions about ad-merge

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

FAQPage Schema

How do I automate GitHub PR merges with CI checks and review gating?▼

Automate GitHub PR merges by evaluating CI status and review outcomes using gh CLI, then applying an auto-detected merge strategy. The workflow performs preflight checks to ensure CI passes and approvals exist before safely executing the merge.

Can I automatically delete a branch after a GitHub pull request merge?▼

Yes, you can delete a branch after a GitHub pull request merge by executing the gh pr merge command with the --delete-branch flag. This ensures feature branches are cleaned up automatically once the merge is successfully completed.

How does auto-detected merge strategy work for GitHub pull requests?▼

The auto-detected merge strategy selects between squash, rebase, or merge commits based on the PR context. It evaluates the pull request status via gh api to determine the most appropriate method for landing the changes.

What is needed to evaluate a GitHub PR before merging?▼

To evaluate a GitHub PR before merging, you need the gh CLI to satisfy preflight checks and retrieve PR status. The evaluation checks CI results, review approvals, and detects linked tasks or ADR references to ensure it is mergeable.

Does this PR merge automation work without additional GitHub dependencies?▼

Yes, this PR merge automation works without additional dependencies because it relies entirely on the gh CLI. It uses gh pr and gh api commands to retrieve status, evaluate checks, and execute the merge directly.

When should I not use automated GitHub PR merging?▼

You should not use automated GitHub PR merging when a pull request requires manual intervention, has failing CI checks, or lacks the necessary review approvals. The workflow enforces these gates and will not merge if preflight conditions are unmet.