skills.rest
MayMustAI
MayMustAIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

merge

Squash-merge GitHub PRs after validating author, approvals, and status checks.

1|Updated Apr 22, 2026
Search Tags:#git#workflow#merge#squash#gate#pull-request
One-click install
npx skills add https://github.com/MayMustAI/ai-dev-playbook --skill merge-maymustai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/MayMustAI/ai-dev-playbook/tree/main/plugins/maymust/skills/merge
Command: npx skills add https://github.com/MayMustAI/ai-dev-playbook --skill merge-maymustai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces team squash-merge policy and a gated PR workflow to prevent common merge mistakes, ensuring a clean, traceable history in the main branch.

Core Features & Use Cases

  • Gate-driven merge: validates PR existence and openness, author identity, mergeability, required reviews, status checks, and base branch before proceeding.
  • Clean squash messages: strips non-essential sections (like Self-verification and Screenshots) from the PR body to produce a concise, traceable squash commit message.
  • Local/remote hygiene: after a successful merge, synchronizes the dev branch and cleans up the feature branch to keep the repository tidy.

Quick Start

Run /maymust:merge to merge the current PR after all gates pass.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate squash-merge for GitHub pull requests while enforcing approval checks?▼

Automating squash-merge for GitHub pull requests involves validating the author, mergeable state, required reviews, and status checks before merging. This skill enforces those gate checks and generates a clean squash commit message by stripping non-essential sections from the PR body.

What is the best way to keep a clean git history when merging feature branches into dev?▼

Keeping a clean git history when merging feature branches requires squash-merging to compress commits and stripping non-essential PR body sections like self-verification. This approach ensures a concise, traceable commit history in the main branch while cleaning up the feature branch afterward.

How does a gated pull request workflow prevent common merge mistakes?▼

A gated pull request workflow prevents merge mistakes by validating PR existence, author identity, mergeability, required reviews, status checks, and base branch before proceeding. This ensures only fully compliant PRs are squash-merged into the dev branch.

Can I validate the base branch and required reviews before squash-merging a PR?▼

Validating the base branch and required reviews before squash-merging a PR is supported through gate-driven checks. The workflow confirms the PR is open, mergeable, and has passed all required status checks and approvals before performing the merge.

How do I clean up feature branches and synchronize the local dev branch after a merge?▼

Cleaning up feature branches and synchronizing the local dev branch after a merge happens automatically once the squash-merge succeeds. The workflow removes the remote feature branch and pulls the latest dev branch to maintain repository hygiene.

Why does my squash commit message include unwanted PR sections like screenshots?▼

Squash commit messages include unwanted PR sections when non-essential text is not stripped. This skill solves that by removing sections like Self-verification and Screenshots from the PR body, producing a concise and traceable commit message.

Related Skills

Explore More Software Engineering Skills→
SeanHoggSeanHogg
3

merge-pr

Squash-merge GitHub pull requests with validation and cleanup.

Community
Advanced
aberrantCodeaberrantCode
1

git-cleanup

Audit and remove stale git worktrees and branches merged into dev.

Community
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
mjbellantonimjbellantoni

squash-merge

Draft standardized commit messages and squash merge GitHub pull requests via gh CLI.

Community
Intermediate