merge-pr
Skill0 starsChanged 49 days agoMITView on GitHub
Merge current PR after CI passes. Waits for all checks, squash merges, deletes branch, switches to main.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- mihai-dinculescu/tapotheir own version, first seen Nov 9, 2026
- ddnexus/pagytheir own version, first seen Nov 9, 2026
- ShareX/ShareXtheir own version, first seen Nov 8, 2026
- kdy1/kdy1-scriptstheir own version, first seen Nov 1, 2026
- r3bl-org/r3bl-open-coretheir own version, first seen Oct 17, 2026
- jsirish/workflow-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use implement-issue, create-pr and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillimplement-issue
Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.
Also in 3 projects that use this
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 7 projects that use this
sahinSkillcreate-issue
Also in 3 projects that use this
- SentrySkill
commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- ShareX/ShareX★ 41ksame name
- cube-js/cube★ 21ksame name
- ddnexus/pagy★ 5ksame name
- mihai-dinculescu/tapo★ 870same name
- bazel-contrib/rules_python★ 692same name
- kkokosa/dotLLM★ 528same name
- r3bl-org/r3bl-open-core★ 486same name
- tbhb/vale-ai-tells★ 118same name
- TermiX-official/cryptoclaw★ 100same name
- kdy1/kdy1-scripts★ 33same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-fullSkill
- frontend-designSkill
- parallel-builderSkill
- pushSkill
- review-code-fixSkill
- review-docsSkill
- review-fullSkill
- review-ux-fixSkill
- shipSkill
- skill-creatorSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Wait for CI, then merge cleanly.
- Distinctive: line 22
Never merges with failing CI: if checks fail, report which ones and stop
- Very specific: line 24
Always deletes branch: no stale branches (remove --delete-branch if you want to keep them)
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/merge-pr
Wait for CI, then merge cleanly.
Workflow
- Get current PR:
gh pr viewon current branch - Wait for CI: poll every 15s until all checks pass
- Squash merge:
gh pr merge --squash --delete-branch - Switch to main:
git checkout main && git pull --rebase - Report: confirm merge succeeded
Rules
<!-- CONFIGURE: Change merge strategy (--squash, --merge, --rebase) and branch cleanup to match your workflow -->- Never merges with failing CI: if checks fail, report which ones and stop
- Always squash merge: keeps main history clean (change to
--mergeor--rebaseif preferred) - Always deletes branch: no stale branches (remove
--delete-branchif you want to keep them) - Never merges to non-default branch: PR must target
main(or your default branch)
Usage
/merge-pr # Merge current branch's PRDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.