agentsclimarketplace

Gh pr merge

Skill dceoy/github-cli-agent-skills/skills/gh-pr-merge

Agent skills for GitHub CLI

Install
npx -y skills add dceoy/github-cli-agent-skills --skill gh-pr-merge

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Merge GitHub pull requests using gh CLI with merge, squash, or rebase strategies and optional auto-merge.

SKILL.md

1.2 KB, 272 tokens by cl100k_base, as published. Nobody here has run it

GitHub PR Merge

When to use

  • The user asks to merge an approved PR.
  • You need to enable auto-merge.

Inputs to confirm

  • PR number/URL/branch (or use current branch PR).
  • Merge strategy: --merge, --squash, or --rebase.
  • Whether to delete the branch, use auto-merge, or use admin override.

Workflow

  1. Verify auth and PR status:
    gh --version
    gh auth status
    gh pr view 123
    
  2. Merge:
    gh pr merge 123 --squash
    gh pr merge 123 --merge --delete-branch
    
  3. Enable auto-merge if required checks are pending:
    gh pr merge 123 --auto --squash
    

Examples

# Squash merge and delete branch
~ gh pr merge 123 --squash --delete-branch

Notes

  • If a merge queue is required, gh pr merge will use it automatically.
  • Use --admin only when you have permission to bypass requirements.

References

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most pr commit review skills give in 272 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

  • Use conventional commits formatin 127 of 888, across 115 files
  • Keep subject line under 72 charactersin 62 of 888, across 48 files
  • Delete branches after mergein 51 of 888, across 38 files
  • Use imperative mood in subject linein 51 of 888, across 42 files
  • Use imperative mood in commit messagesin 44 of 888
  • Verify directory is ignored before creating worktreein 43 of 888, across 12 files
  • Generate a conventional commit messagein 43 of 888
  • Add unignored worktree directories to gitignorein 42 of 888, across 10 files
  • Make atomic commitsin 39 of 888, across 27 files
  • Run tests before committingin 36 of 888, across 25 files
  • Verify clean test baselinein 35 of 888, across 9 files
  • Split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

  • Confirm the merge strategy
  • Confirm auto-merge usage
  • Confirm admin override usage
  • Execute the PR merge
  • Enable auto-merge for pending checks
  • Use --admin only with bypass permission

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.