skills.rest
a-tabiji
a-tabijiCOMMUNITY
Explore all skills by this author →
GitHub

merge

Merge reviewed pull requests into main with squash merge and branch cleanup.

Updated Apr 30, 2025
Search Tags:#workflow#github#merge#branch#pr#squash#ci
One-click install
npx skills add https://github.com/a-tabiji/atima-lp --skill merge-a-tabiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/a-tabiji/atima-lp/tree/main/.claude/skills/merge
Command: npx skills add https://github.com/a-tabiji/atima-lp --skill merge-a-tabiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge a reviewed PR into main via squash merge, streamlining the workflow and ensuring a clean commit history.

Core Features & Use Cases

  • Automated PR readiness checks: verifies LGTM status and CI checks before merging.
  • Squash merge and branch cleanup: performs a single-commit merge and deletes the source branch.
  • Workflow integration: closes related issues when specified and triggers deployment pipelines on main updates.

Quick Start

Execute the merge command to squash and merge PR #<PR_NUMBER> into main, then confirm deployment.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I squash merge a pull request into the main branch automatically?▼

To automate squash merging a pull request, this Skill checks PR readiness including LGTM and CI status, performs the squash merge into main, and cleans up the source branch.

Can my squash merge workflow close related GitHub issues automatically?▼

Yes, the squash merge workflow can close related GitHub issues automatically. When issues are specified, the Skill closes them after successfully merging the PR into the main branch.

What is checked before a PR is squash merged into the main branch?▼

Before a PR is squash merged, the Skill performs automated readiness checks that verify LGTM status and CI checks to ensure the pull request is safe to merge into main.

Do I need GitHub CLI installed to automate squash merging pull requests?▼

Yes, you need GitHub CLI (gh) access and repository permissions to automate squash merging. The Skill uses gh to run readiness checks, perform merges, and execute branch deletions.

What is the best way to clean up branches after a squash merge on GitHub?▼

The best way to clean up branches after a squash merge is to automate source branch deletion. This Skill performs the squash merge and removes the branch to maintain a clean repository.

Squash merge workflow: when should I avoid automating PR merges?▼

You should avoid automating PR squash merges if your repository lacks GitHub CLI access or if your CI checks and LGTM status are not reliably configured to gate the main branch.

Related Skills

Explore More Software Engineering Skills→
mir-ammir-am
1

gh-protect-default-branch

Automate branch protection enforcement on GitHub repositories via gh CLI.

Community
Basic
smallorbitsmallorbit

merge-pr

Squash-merge the open PR for the current branch and delete the remote branch.

Community
Intermediate
drillandrillan
1

merge-pr

Wait for CI checks and merge GitHub pull requests with a chosen strategy.

Community
Advanced
tjmgregorytjmgregory

squash-merge

Squash merge GitHub pull requests via gh CLI with conventional commit messages.

Community
Advanced