skills.rest
joeczar
joeczarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

auto-merge

Rebase a PR onto main, run review pass, verify CI, and merge.

Updated Jan 18, 2026
Search Tags:#automation#merge#pr#code-review#ci
One-click install
npx skills add https://github.com/joeczar/code-graph-mcp --skill auto-merge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-merge
Source: https://github.com/joeczar/code-graph-mcp/tree/main/.claude/skills/auto-merge
Command: npx skills add https://github.com/joeczar/code-graph-mcp --skill auto-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges a PR automatically after rebasing, running review-pass, verifying CI, and addressing comments to streamline code integration.

Core Features & Use Cases

  • Rebase PR onto latest main and ensure a clean working tree.
  • Run mandatory review pass to identify and fix issues across code quality and tests.
  • Verify CI status and merge when checks pass, with optional configurations.

Quick Start

Invoke the auto-merge workflow with a PR number to begin the automated merge process.

Frequently Asked Questions about auto-merge

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

FAQPage Schema
How do I automatically merge a pull request after CI passes?▼

To automatically merge a pull request, the workflow rebases the branch onto main, runs a mandatory review pass, verifies CI checks are green, and applies a configurable merge strategy to ensure safe integration.

What is the safest way to automate PR merges without breaking the main branch?▼

Safe PR merges require rebasing onto the latest main branch, resolving review comments, and verifying CI status is green before applying the merge strategy to prevent integration failures.

Can I trigger an automated merge workflow for any open PR?▼

Automated merging applies to open PRs targeting main that are ready for merge, requiring CI to be green and review comments to be resolved before proceeding with the rebase and integration.

How does the automated review pass work before a PR is merged?▼

The review pass runs automatically to identify and fix issues across code quality and tests, ensuring the codebase remains stable before verifying CI status and completing the PR merge.

What happens if CI checks fail during an automated PR merge?▼

If CI checks fail, the automated PR merge halts to ensure safe integration; the workflow requires CI to be green and review comments to be resolved before proceeding with the merge.

Do I need to manually rebase my branch before starting the auto-merge process?▼

No manual rebase is needed; the auto-merge workflow automatically rebases your PR onto the latest main branch to ensure a clean working tree before running reviews and verifying CI.

Related Skills

Explore More Software Engineering Skills→
gewoonsebagewoonseba
9

babysit

Rebase open pull requests on main, address review comments, and fix failing CI.

Community
Advanced
sanruizsanruiz

GitHub Release Workflow

Automate GitHub release workflows with pre-release checks, branch creation, version updates, and tagging.

Community
Advanced
jimmymalhanjimmymalhan
1

auto-merge

Merge pull requests automatically after CI checks pass.

Community
Intermediate
ksciuskscius
2

fix-merge-conflicts

Resolve Git merge conflicts and verify buildable, test-passing state.

Community
Advanced