auto-merge

Create or remove the attended auto-merge approval marker file for Claude Code sessions.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mckissinger/keel --skill auto-merge-mckissinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-merge
Source: https://github.com/mckissinger/keel/tree/main/skills/auto-merge
Command: npx skills add https://github.com/mckissinger/keel --skill auto-merge-mckissinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes redundant per-merge approval friction during a human-driven session while preserving verified-pin gates, branch protections, and agent safety boundaries.

Core Features & Use Cases

  • Session Toggle Management: Creates or removes the attended auto-merge marker that controls merge approval behavior for the current session.
  • Safety-Preserving Workflow: Keeps verification gates, autonomy restrictions, and merge command limitations intact while allowing explicitly authorized auto merges.
  • Use Case: A developer running a verified build session can enable attended auto-merge so instructed gate-passing pull requests can proceed without repeated approval taps.

Quick Start

Ask the auto-merge skill to enable attended auto-merge for the current session.

Frequently Asked Questions about auto-merge

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

FAQPage Schema
How do I stop repetitive merge approval confirmations during a Claude Code build session?

You can enable the attended auto-merge marker for your current session to reduce redundant per-merge approval friction while preserving verification gates and branch protections.

Is it safe to enable auto-merge for pull requests in an attended Claude Code session?

Yes, enabling auto-merge in an attended session preserves verified-pin gates, autonomy restrictions, and merge command limitations while only writing or removing the authorized merge marker file.

How do I toggle auto-merge authorization for a specific GitHub workflow session?

Ask the auto-merge skill to create or remove the attended merge marker file to control merge approval behavior for the current human-driven session scope.

Does enabling auto-merge execute the pull request merge directly?

No, this process requires writing or removing only the attended merge marker file with validation-compatible fields and performs no direct merge execution.

Can I use auto-merge to bypass branch protections and verification gates during a pull request workflow?

No, the auto-merge workflow keeps verification gates, branch protections, and agent safety boundaries intact while allowing explicitly authorized auto merges to proceed.

When should I not use the auto-merge marker for my pull requests?

You should not use this marker for fully autonomous operations, as it applies specifically to human-driven Claude Code build sessions that need controlled pull request merge authorization.