skills.rest
oogDZ
oogDZCOMMUNITY
Explore all skills by this author →
GitHub

merge

Merge GitHub pull requests with pre- and post-merge validations.

Updated Apr 2, 2026
Search Tags:#automation#workflow#github#validation#merge#pull-request
One-click install
npx skills add https://github.com/oogDZ/2 --skill merge-oogdz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/merge
Command: npx skills add https://github.com/oogDZ/2 --skill merge-oogdz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge requests manually is error-prone and time-consuming. This Skill automates pre- and post-merge checks and ensures main branch synchronization and cleanup, reducing drift and risk.

Core Features & Use Cases

  • Pre- and post-merge validations to ensure PR quality and conformity with standards.
  • Main branch synchronization after merge to maintain a clean history.
  • Cleanup of branches and references to keep repository hygiene in check.

Quick Start

Create a pull request number and use the /merge command to perform an automated merge with validations.

Frequently Asked Questions about merge

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

FAQPage Schema
How do I automate a GitHub pull request merge with validation checks?▼

Automate a GitHub pull request merge by providing a PR number to trigger pre-merge validations, execute the merge, synchronize the main branch, and cleanup references automatically.

What is the best way to synchronize the main branch after merging a pull request?▼

Synchronize the main branch after merging a pull request by running an automated post-merge workflow that aligns repository history and performs branch cleanup to maintain hygiene.

How do I run pre-merge and post-merge validations on GitHub pull requests?▼

Run pre-merge and post-merge validations on GitHub pull requests using an automated workflow that applies SSOT-guided checks to ensure conformity and reduce drift before finalizing the merge.

Does this automated merge workflow require a specific pull request number?▼

Yes, the automated merge workflow requires an active pull request number as input to execute the predefined SSOT-guided merge process with validations and branch cleanup.

Why does manual pull request merging cause repository drift and how to prevent it?▼

Manual pull request merging causes repository drift due to overlooked synchronization and branch cleanup errors; prevent this by automating pre-merge checks and post-merge main branch synchronization.

When should I not use an automated workflow for merging pull requests?▼

Avoid using an automated workflow for merging pull requests if your repository requires custom conflict resolution logic or operates outside standard GitHub PR workflows and SSOT-guided validation constraints.

Related Skills

Explore More Software Engineering Skills→
a-tabijia-tabiji

merge

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

Community
Intermediate
pkuppenspkuppens
1

branch-cleanup

Automates Git branch cleanup and synchronization with the main branch after merges.

Community
Basic
nashgaonashgao
3

Merge Pull Request Command

Merge pull requests into a target branch with validation and quality gates.

Community
Advanced
Sir-chawakornSir-chawakorn
9

resolve-merge-rebase-conflict

Resolve git merge, rebase, and cherry-pick conflicts by combining code hunks.

Community
Advanced