pr-merge
Skill2 starsChanged 11 days agoMITView on GitHub
Merge pull requests that the owner lists explicitly into develop of this repository. Use when the owner says "merge #15, #16" or similar. Rebases each PR onto develop, checks the commits, waits for the six CI jobs and squash-merges with a message that follows rule 12. Not for reviewing, fixing or creating pull requests, and not for release PRs.
- Deletes or force-pushes
- Commits and pushes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- shadok-ai/shadok-aitheir own version, first seen Nov 9, 2026
- mustafarslan/skillstheir own version, first seen Nov 8, 2026
- mia-cx/skillstheir own version, first seen Oct 16, 2026
- symfony/symfonytheir own version, first seen Oct 8, 2026
- HKUDS/OpenHarnesstheir own version, first seen Oct 8, 2026
- genlayerlabs/skillstheir own version, first seen Jul 29, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- symfony/symfony★ 31ksame name
- HKUDS/OpenHarness★ 16ksame name
- genlayerlabs/skills★ 19same name
- shadok-ai/shadok-ai★ 14same name
- huangqianqian120/NexusAgent★ 9same name
- mia-cx/skills★ 4same name
- mustafarslan/skills★ 2same name
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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- coagent8-workflowSkill
- coagent8-consultSkill
- coagent8-delegateSkill
- coagent8-doctorSkill
- coagent8-issueSkill
- coagent8-loopSkill
- coagent8-reviewSkill
- coagent8-sessionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 4 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Run each command as its own terminal call.
- Very specific: line 25
Never open an editor: continue a rebase with git -c core.editor=true rebase --continue.
- Very specific: line 27
Never use git stash, git worktree, git merge, git reset, git rebase --skip or git rebase --abort.
- Very specific: line 30
Never push to develop. Push only a listed PR's branch, with a lease bound to the commit you observed (step 7).
- Distinctive: line 32
Never add AI attribution (Co-Authored-By, "Generated with") anywhere.
- Very specific: line 48
Stop unless state is OPEN, baseRefName is develop and isCrossRepository is false (the branch lives in this repository).
- Very specific: line 50
Stop if headRefName starts with release/: a release PR is merged by the owner per rule 12 section 5, and its changelog needs --tag.
- Very specific: line 52
Stop unless the body's Verification section records an independent review with verdict READY in the format of core rule 03.
- Distinctive: line 56
Stop if the PR has an open review finding or unresolved conversation: rebasing is allowed only after the review is complete (rule 12 …
- Very specific: line 62
If mergeStateStatus is CLEAN, go to step 8.
- Distinctive: line 63
Update the branch (each must succeed):
- Very specific: line 110
run the CoAgent8 review tool with scope origin/develop...<branch> and that reviewer's backend (model as the owner named, else the default).
- Very specific: line 117
update the PR body's Verification section with gh pr edit N --body-file <file>: mark the old review line superseded and add the new one in …
- Distinctive: line 124
Write the squash message body (rule 12 section 2) to a file outside the repository, for example in the system temp directory:
- Very specific: line 137
Wait for the CI run of that merge commit: run gh run list --workflow CI --commit <mergeCommit.oid> every two minutes until it lists a …
“Common” is measured: kept by at least 6 in 10 of the 7 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 pull requests into develop
Merging is an owner action (rule 12): run this
only when the owner lists the PR numbers in the request, and merge only those,
one at a time, in the order given (ascending if no order was given). Never touch
any other PR. The owner's list also authorizes rebasing and force-pushing the
listed PRs' branches; it covers nothing else. The standing go-ahead of
2026-11-02 in project.md counts as such a
list for the agent's own clean topic PRs; it does not cover force-pushing.
How to run commands
- Run each command as its own terminal call. Do not chain with
&∨, and do not use command substitution. - Any command that fails or prints something this file does not expect:
stop and report the command and its output. Do not improvise a fix. Two
non-zero exits are expected:
git rebaseandrebase --continuestopping on a conflict (handled in step 5), andgh pr checksexiting with 8 while checks are pending (step 8). - Never open an editor: continue a rebase with
git -c core.editor=true rebase --continue. - Never use
git stash,git worktree,git merge,git reset,git rebase --skiporgit rebase --abort. Merge commits breaknpm run changelog:check; branches are updated by rebase only. - Never push to
develop. Push only a listed PR's branch, with a lease bound to the commit you observed (step 7). - Never add AI attribution (Co-Authored-By, "Generated with") anywhere.
Before the first PR
git status --shortmust be empty. If it is not, stop and report: the files belong to someone else.- Note the current branch (
git branch --show-current) for the report. git fetch origin, thengit rev-parse origin/developgives the currentdevelopcommit;gh run list --workflow CI --commit <that SHA>must list a finished run with conclusionsuccess. If it is red or missing, stop: rule 12 allows no further merge until a fix restores green CI.
For each PR number N
- Read the PR:
gh pr view N --json state,title,body,headRefName,headRefOid,baseRefName,isCrossRepository,mergeStateStatus- Stop unless
stateisOPEN,baseRefNameisdevelopandisCrossRepositoryisfalse(the branch lives in this repository). - Stop if
headRefNamestarts withrelease/: a release PR is merged by the owner per rule 12 section 5, and its changelog needs--tag. - Stop unless the body's Verification section records an independent
review with verdict
READYin the format of core rule 03. If its reviewed head differs fromheadRefOid, step 9 reviews the head again. - Stop if the PR has an open review finding or unresolved conversation: rebasing is allowed only after the review is complete (rule 12 section 3, "Review and merge").
- Remember
title,body,headRefName(the branch) andheadRefOid(the observed head).
- Stop unless
gh pr checks N: stop if any job failed; never rerun jobs.- If
mergeStateStatusisCLEAN, go to step 8. - Update the branch (each must succeed):
git fetch origingit checkout <branch>git pull --ff-onlygit rev-parse HEADmust equalheadRefOid; otherwise stop (someone else changed the branch, or the local copy has unpushed commits).git rebase origin/develop
- Rebase conflicts.
git status --shortlists them; for each conflicted file:CHANGELOG.md: a topic branch must not change it (rule 12 section 6); stop and report.docs/ROADMAP.md: rungit show REBASE_HEAD -- docs/ROADMAP.mdto see the exact edit of the commit being replayed. Keep the<<<<<<< HEADside whole and apply to it exactly that edit (typically an issue link or a status line). Remove all conflict markers and check that none remain, thengit add docs/ROADMAP.md. Stop if the edit does not apply cleanly to the HEAD side (both sides changed the same lines), or if you are unsure.- Any other file: stop and report the file names. Do not resolve code or test conflicts: they need a new review.
- Then
git -c core.editor=true rebase --continue; repeat until the rebase finishes.
- Checks (each must exit 0):
git diff --name-only origin/develop -- CHANGELOG.mdmust print nothing: only a release PR changes the changelog; otherwise stop and report.npm run changelog:check -- --with-commit "<title>"npm run typecheck- For each test file the PR changes
(
git diff --name-only origin/develop -- tests),node tests/run.cjs <file>, which must reportfail 0.
git rev-parse HEADgives the new local head. Push withgit push --force-with-lease=<branch>:<headRefOid> --force-if-includes origin <branch>(rule 12 section 1), thengh pr view N --json headRefOidmust equal the new local head (otherwise stop: someone else pushed). From now onheadRefOidis that SHA.- CI on the current head:
gh pr view N --json headRefOidmust still equalheadRefOid; rungh pr checks Nevery two minutes until no job is pending. Exactly six jobs must be listed and all must bepass, also when step 3 skipped the update. On a failure, stop and report the last 60 lines ofgh run view <run id> --log-failed; never rerun jobs. - Independent review of the current head (core rule 03, rule 13). A rebase or new commit
supersedes earlier review evidence. Reuse the review recorded in the PR body
only if it names head
headRefOid, scope<base>...<head>with base equal togit merge-base origin/develop <headRefOid>(the whole PR, not one commit), coverageCOMPLETEand 0 unresolved P1/P2, for every required reviewer inproject.md(Codex and agy). Otherwise, for each required reviewer without such a review:git fetch origin,git checkout <branch>,git pull --ff-only;git rev-parse HEADmust equalheadRefOid;- run the CoAgent8
reviewtool with scopeorigin/develop...<branch>and that reviewer's backend (model as the owner named, else the default); - require
VERDICT: READYandCOVERAGE: COMPLETE; onBLOCKED, stop and report the findings (do not fix them: that is the Author's work); - afterwards
git rev-parse HEADandgh pr view N --json headRefOidmust both still equalheadRefOid, else the review covered another snapshot: stop; - update the PR body's Verification section with
gh pr edit N --body-file <file>: mark the old review line superseded and add the new one in the core rule 03 format (verdict, head, base, scope, coverage, unresolved P1/P2, session handle as evidence). Change nothing else in the body.
gh pr view N --json mergeStateStatusmust beCLEAN; if it isBEHINDagain, go back to step 4.CLEANalso means that the ruleset's conditions (resolved conversations, required checks) hold.- Write the squash message body (rule 12 section 2) to a file outside the
repository, for example in the system temp directory:
- the text of the PR body's
## Summarysection (why the change is needed and what behavior changes), wrapped at 72 characters; - a blank line, then one footer per line, collected from the whole PR
body:
Fixes #123,Refs #123,Refs: <roadmap card>and everyBREAKING CHANGE:footer; - nothing else: no Verification table, checklist, file list or AI attribution. Stop if the Summary is missing or a footer is ambiguous.
- the text of the PR body's
gh pr merge N --squash --match-head-commit <headRefOid> --subject "<title> (#N)" --body-file <file>. The repository deletes the merged branch itself.gh pr view N --json state,mergeCommit:statemust beMERGED; remembermergeCommit.oid. Delete the message file.- Wait for the CI run of that merge commit: run
gh run list --workflow CI --commit <mergeCommit.oid>every two minutes until it lists a finished run, and require conclusionsuccessbefore the next PR. If it is red, stop the batch and report: the cause is found and fixed in a new PR before anything else is merged.
Report
A table: PR, title, conflicts and how they were resolved, local checks
(PASS/FAIL with the command), CI result, merged yes/no, develop CI after the
merge. Name every step that was skipped and why, and the branch noted at the
start.
Does 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.

