skills.rest
FatBy
FatByCOMMUNITY
Explore all skills by this author →
GitHub

merge-pr

Merge GitHub pull requests after validating required checks and pinning the head commit.

2|Updated Feb 13, 2026
Search Tags:#automation#git#ci/cd#github#merge#pr
One-click install
npx skills add https://github.com/FatBy/DD-OS --skill merge-pr-fatby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-pr
Source: https://github.com/FatBy/DD-OS/tree/main/skills/agent-merge-pr
Command: npx skills add https://github.com/FatBy/DD-OS --skill merge-pr-fatby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of merging GitHub pull requests in a secure and deterministic manner, ensuring all checks pass and maintaining accurate attribution.

Core Features & Use Cases

  • Script-first Validation: Ensures PRs meet all required checks before merging.
  • Deterministic Squash Merge: Pins the merge to a specific commit SHA for reliability.
  • Attribution and Commenting: Correctly attributes the merge and adds necessary comments.
  • Use Case: A developer has prepared a pull request and wants to merge it automatically after all CI checks have passed, ensuring the merge is clean and properly documented.

Quick Start

Use the merge-pr skill to verify and run the merge for pull request number 123.

Frequently Asked Questions about merge-pr

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

FAQPage Schema
How do I automate merging a GitHub pull request only after CI checks pass?▼

Automating a GitHub pull request merge is handled through a script-first validation approach that gates the merge on required CI checks. It ensures all conditions are met before proceeding with the merge.

How do I pin a GitHub PR merge to a specific commit SHA for deterministic results?▼

Pinning a PR merge to a specific commit SHA is achieved via a deterministic squash merge process. This locks the merge to the exact head-commit, ensuring reliable and verifiable integration into the repository.

What is the best way to ensure proper attribution and commenting when merging a PR?▼

Ensuring proper attribution and commenting during a PR merge is managed automatically by the skill. It handles the merge commit attribution and posts the necessary documentation comments to the pull request.

Does this PR merge process provide a manual fallback for GitHub repositories?▼

A manual fallback option is supported alongside the wrapper commands for GitHub repositories. This allows developers to manually intervene and execute the merge if the automated deterministic wrapper encounters issues.

How does the automated PR merge handle cleanup after a successful integration?▼

Cleanup after a successful PR merge is executed through robust post-merge procedures. The skill automatically handles repository cleanup to maintain a clean state following the deterministic squash merge.

Can I use this to validate required GitHub PR checks before a squash merge?▼

Validating required GitHub PR checks is a core capability before performing a squash merge. The script-first validation strictly gates the process, guaranteeing no merge occurs unless all defined checks pass.

Related Skills

Explore More Software Engineering Skills→
ajsai47ajsai47
11

land-and-deploy

Merge GitHub pull requests and verify production health after deployment.

Community
Advanced
rajveersingh11rajveersingh11

post-merge-scan

Scan merge commit messages for TODOs, deprecated APIs, broken links, and stale flags.

Community
Basic
mvillmowmvillmow
18

verify-pr-ready

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

Community
Basic
adoreseveradoresever
202

merge-pr

Squash-merge prepared GitHub PRs with exact head-commit matching and cleanup.

Community
Advanced