How do I install the Merge Pr skill?

Run npx skillmds@latest add sheshiyer/merge-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Merge Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Merge Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Merge Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Merge Pr?

Sheshiyer (@sheshiyer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Merge Pr by sheshiyer — Agent Skill

Name: Merge Pr
Author: Sheshiyer

Merge Pr

Script-first deterministic squash merge with strict required-check gating, head-SHA pinning, and reliable attribution and commenting. USE WHEN squash-merging a pull request safely, enforcing required status checks before merge, or pinning to a head SHA to avoid merging unexpected new commits.

Sheshiyer Updated Sep 17, 2026

File contents

Merge PR

Overview

Merge a prepared PR only after deterministic validation.

Inputs

Ask for PR number or URL.
If missing, use .local/prep.env from the PR worktree.

Safety

Never use gh pr merge --auto in this flow.
Never run git push directly.
Require --match-head-commit during merge.
Wrapper commands are cwd-agnostic; you can run them from repo root or inside the PR worktree.

Execution Contract

Validate merge readiness:

scripts/pr-merge verify <PR>

Backward-compatible verify form also works:

scripts/pr-merge <PR>

Run one-shot deterministic merge:

scripts/pr-merge run <PR>

Ensure output reports:

merge_sha=<sha>
merge_author_email=<email>
comment_url=<url>

Steps

Validate artifacts

require=(.local/review.md .local/review.json .local/prep.md .local/prep.env)
for f in "${require[@]}"; do
  [ -s "$f" ] || { echo "Missing artifact: $f"; exit 1; }
done

Validate checks and branch status

scripts/pr-merge verify <PR>
source .local/prep.env

scripts/pr-merge treats “no required checks configured” as acceptable ([]), but fails on any required fail or pending.

Merge deterministically (wrapper-managed)

scripts/pr-merge run <PR>

scripts/pr-merge run performs:

deterministic squash merge pinned to PREP_HEAD_SHA
reviewer merge author email selection with fallback candidates
one retry only when merge fails due to author-email validation
co-author trailers for PR author and reviewer
post-merge verification of both co-author trailers on commit message
PR comment retry (3 attempts), then comment URL extraction
cleanup after confirmed MERGED

Manual fallback (only if wrapper is unavailable)

scripts/pr merge-run <PR>

Cleanup

Cleanup is handled by run after merge success.

Guardrails

End in MERGED, never CLOSED.
Cleanup only after confirmed merge.

---name: merge-prdescription: Script-first deterministic squash merge with strict required-check gating, head-SHA pinning, and reliable attribution and commenting. USE WHEN squash-merging a pull request safely, enforcing required status checks before merge, or pinning to a head SHA to avoid merging unexpected new commits.---# Merge PR## OverviewMerge a prepared PR only after deterministic validation.## Inputs- Ask for PR number or URL.- If missing, use `.local/prep.env` from the PR worktree.## Safety- Never use `gh pr merge --auto` in this flow.- Never run `git push` directly.- Require `--match-head-commit` during merge.- Wrapper commands are cwd-agnostic; you can run them from repo root or inside the PR worktree.## Execution Contract1. Validate merge readiness:```shscripts/pr-merge verify <PR>```Backward-compatible verify form also works:```shscripts/pr-merge <PR>```2. Run one-shot deterministic merge:```shscripts/pr-merge run <PR>```3. Ensure output reports:- `merge_sha=<sha>`- `merge_author_email=<email>`- `comment_url=<url>`## Steps1. Validate artifacts```shrequire=(.local/review.md .local/review.json .local/prep.md .local/prep.env)for f in "${require[@]}"; do [ -s "$f" ] || { echo "Missing artifact: $f"; exit 1; }done```2. Validate checks and branch status```shscripts/pr-merge verify <PR>source .local/prep.env````scripts/pr-merge` treats “no required checks configured” as acceptable (`[]`), but fails on any required `fail` or `pending`.3. Merge deterministically (wrapper-managed)```shscripts/pr-merge run <PR>````scripts/pr-merge run` performs:- deterministic squash merge pinned to `PREP_HEAD_SHA`- reviewer merge author email selection with fallback candidates- one retry only when merge fails due to author-email validation- co-author trailers for PR author and reviewer- post-merge verification of both co-author trailers on commit message- PR comment retry (3 attempts), then comment URL extraction- cleanup after confirmed `MERGED`4. Manual fallback (only if wrapper is unavailable)```shscripts/pr merge-run <PR>```5. CleanupCleanup is handled by `run` after merge success.## Guardrails- End in `MERGED`, never `CLOSED`.- Cleanup only after confirmed merge.

Frequently asked questions