merge

Push a feature branch, create a GitHub PR into develop, and squash-merge after CI checks pass.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/benjaminfauchald/Tracklister --skill merge-benjaminfauchald
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/benjaminfauchald/Tracklister/tree/main/.claude/skills/merge
Command: npx skills add https://github.com/benjaminfauchald/Tracklister --skill merge-benjaminfauchald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates pushing a local feature branch, creating or locating a GitHub pull request targeting develop, waiting for required CI checks to pass, and performing the merge so developers don't need to perform these repetitive CLI steps manually.

Core Features & Use Cases

  • State validation: Confirms the current branch is not main or develop and that there are no uncommitted changes before proceeding.
  • PR management: Pushes the branch, finds an existing PR or creates a new concise PR into develop using commit summaries for title and body.
  • CI orchestration and merge: Polls required CI checks until they pass or fail, aborts on failing checks with actionable errors, and performs a squash merge with branch deletion, retrying with admin privileges if branch protection blocks the merge.
  • Use Case: Ideal for developers and CI operators who want a reliable, unattended workflow to merge completed feature branches into develop once automated tests pass.

Quick Start

Ask the merge skill to push the current branch, open or create a PR into develop, wait for required CI checks, and merge on success.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate pushing a git branch and merging a pull request into develop?

To automate pushing a git branch and merging a pull request, you need a workflow tool that pushes your local branch, creates a PR into develop, and performs a squash merge automatically.

Can I automatically merge a GitHub pull request only after CI checks pass?

Yes, you can automatically merge a GitHub pull request after CI checks pass by using an automation tool that polls required CI validations and aborts the merge if any checks fail.

Does the merge automation work with the gh CLI for GitHub branch management?

Yes, the merge automation works with the gh CLI for GitHub branch management by using it to locate or create pull requests and perform squash merges with branch deletion.

What is the best way to handle branch protection rules when automating a squash merge?

The best way to handle branch protection rules when automating a squash merge is to use a tool that retries the merge with admin privileges if the initial attempt is blocked by protection settings.

Why does automated branch merging abort when there are uncommitted local changes?

Automated branch merging aborts when there are uncommitted local changes because state validation requires a clean working directory before pushing a feature branch to origin.

Do I need to manually create a pull request before running merge automation into develop?

No, you do not need to manually create a pull request before running merge automation because it will find an existing PR or automatically create a new concise one using commit summaries.