prepare-pr
Skill100 starsChanged 9 months agoMITView on GitHub
Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /reviewpr. Never merge or push to main.
- Deletes or force-pushes
- Installs packages
- Commits and pushes
We split this skill into the rules it gives an agent
36 rules. 0 are common, 24 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
24
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 14
Ask for PR number or URL.
- Distinctive: line 15
If missing, auto-detect from conversation.
- Very specific: line 20
Never push to main or origin/main.
- Distinctive: line 21
Never run git push without specifying remote and branch explicitly.
- Distinctive: line 22
Do not run gateway stop commands.
- Distinctive: line 23
Do not run git clean -fdx.
- Distinctive: line 24
Do not run git add -A or git add ..
- Distinctive: line 29
If delegating, require the delegate to run commands and capture outputs.
- Very specific: line 33
If you see "fatal: not a git repository", you are in the wrong directory.
- Distinctive: line 35
Do not run git add -A or git add ..
- Distinctive: line 41
Run gates and pass.
- Very specific: line 44
Write .local/prep.md with a prep summary.
- Distinctive: line 49
Create a checklist of all prep steps, print it, then continue and execute the commands.
- Distinctive: line 53
Use an isolated worktree for all prep work.
- Distinctive: line 63
Run all commands inside the worktree directory.
- Very specific: line 110
Run git add <resolved_file> for each file.
- Distinctive: line 113
If the rebase gets confusing or you resolve conflicts 3 or more times, stop and report.
- Very specific: line 121
Keep a running log in .local/prep.md:
- Very specific: line 127
Update CHANGELOG.md if flagged in review
- Very specific: line 129
Check .local/review.md section H for guidance.
- Distinctive: line 130
If flagged and user-facing:
- Very specific: line 132
Check if CHANGELOG.md exists.
- Distinctive: line 139
Add a concise entry with PR number and contributor.
- Distinctive: line 141
Update docs if flagged in review
- Very specific: line 143
Check .local/review.md section G for guidance.
- Distinctive: line 144
If flagged, update only docs related to the PR changes.
- Very specific: line 160
If committer is not found:
- Distinctive: line 166
Run full gates before pushing
- Distinctive: line 194
Verify PR is not behind main (Mandatory)
- Distinctive: line 203
If still behind main, repeat steps 2 through 9.
- Distinctive: line 205
Write prep summary artifacts (Mandatory)
- Very specific: line 215
Create or overwrite .local/prep.md and verify it exists and is non-empty:
- Distinctive: line 234
If gates passed and push succeeded, print exactly:
- Very specific: line 245
Do not delete the worktree on success.
- Distinctive: line 247
Never push to main. Only push to the PR head branch.
- Distinctive: line 248
Run and pass all gates before pushing.
“Common” is measured: kept by at least 6 in 10 of the 11 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
Prepare PR
Overview
Prepare a PR branch for merge with review fixes, green gates, and an updated head branch.
Inputs
- Ask for PR number or URL.
- If missing, auto-detect from conversation.
- If ambiguous, ask.
Safety
- Never push to
mainororigin/main. Push only to the PR head branch. - Never run
git pushwithout specifying remote and branch explicitly. Do not run baregit push. - Do not run gateway stop commands. Do not kill processes. Do not touch port 18792.
- Do not run
git clean -fdx. - Do not run
git add -Aorgit add .. Stage only specific files changed.
Execution Rule
- Execute the workflow. Do not stop after printing the TODO checklist.
- If delegating, require the delegate to run commands and capture outputs.
Known Footguns
- If you see "fatal: not a git repository", you are in the wrong directory. Use
~/openclaw. - Do not run
git clean -fdx. - Do not run
git add -Aorgit add ..
Completion Criteria
- Rebase PR commits onto
origin/main. - Fix all BLOCKER and IMPORTANT items from
.local/review.md. - Run gates and pass.
- Commit prep changes.
- Push the updated HEAD back to the PR head branch.
- Write
.local/prep.mdwith a prep summary. - Output exactly:
PR is ready for /mergepr.
First: Create a TODO Checklist
Create a checklist of all prep steps, print it, then continue and execute the commands.
Setup: Use a Worktree
Use an isolated worktree for all prep work.
cd ~/openclaw
# Sanity: confirm you are in the repo
git rev-parse --show-toplevel
WORKTREE_DIR=".worktrees/pr-<PR>"Run all commands inside the worktree directory.
Load Review Findings (Mandatory)
if [ -f .local/review.md ]; then
echo "Found review findings from /reviewpr"
else
echo "Missing .local/review.md. Run /reviewpr first and save findings."
exit 1
fi
# Read it
sed -n '1,200p' .local/review.mdSteps
- Identify PR meta (author, head branch, head repo URL)
gh pr view <PR> --json number,title,author,headRefName,baseRefName,headRepository,body --jq '{number,title,author:.author.login,head:.headRefName,base:.baseRefName,headRepo:.headRepository.nameWithOwner,body}'
contrib=$(gh pr view <PR> --json author --jq .author.login)
head=$(gh pr view <PR> --json headRefName --jq .headRefName)
head_repo_url=$(gh pr view <PR> --json headRepository --jq .headRepository.url)- Fetch the PR branch tip into a local ref
git fetch origin pull/<PR>/head:pr-<PR>- Rebase PR commits onto latest main
# Move worktree to the PR tip first
git reset --hard pr-<PR>
# Rebase onto current main
git fetch origin main
git rebase origin/mainIf conflicts happen:
- Resolve each conflicted file.
- Run
git add <resolved_file>for each file. - Run
git rebase --continue.
If the rebase gets confusing or you resolve conflicts 3 or more times, stop and report.
- Fix issues from
.local/review.md
- Fix all BLOCKER and IMPORTANT items.
- NITs are optional.
- Keep scope tight.
Keep a running log in .local/prep.md:
- List which review items you fixed.
- List which files you touched.
- Note behavior changes.
- Update
CHANGELOG.mdif flagged in review
Check .local/review.md section H for guidance.
If flagged and user-facing:
- Check if
CHANGELOG.mdexists.
ls CHANGELOG.md 2>/dev/null- Follow existing format.
- Add a concise entry with PR number and contributor.
- Update docs if flagged in review
Check .local/review.md section G for guidance.
If flagged, update only docs related to the PR changes.
- Commit prep fixes
Stage only specific files:
git add <file1> <file2> ...Preferred commit tool:
committer "fix: <summary> (#<PR>) (thanks @$contrib)" <changed files>If committer is not found:
git commit -m "fix: <summary> (#<PR>) (thanks @$contrib)"- Run full gates before pushing
pnpm install
pnpm build
pnpm ui:build
pnpm check
pnpm testRequire all to pass. If something fails, fix, commit, and rerun. Allow at most 3 fix and rerun cycles. If gates still fail after 3 attempts, stop and report the failures. Do not loop indefinitely.
- Push updates back to the PR head branch
# Ensure remote for PR head exists
git remote add prhead "$head_repo_url.git" 2>/dev/null || git remote set-url prhead "$head_repo_url.git"
# Use force with lease after rebase
# Double check: $head must NOT be "main" or "master"
echo "Pushing to branch: $head"
if [ "$head" = "main" ] || [ "$head" = "master" ]; then
echo "ERROR: head branch is main/master. This is wrong. Stopping."
exit 1
fi
git push --force-with-lease prhead HEAD:$head- Verify PR is not behind main (Mandatory)
git fetch origin main
git fetch origin pull/<PR>/head:pr-<PR>-verify --force
git merge-base --is-ancestor origin/main pr-<PR>-verify && echo "PR is up to date with main" || echo "ERROR: PR is still behind main, rebase again"
git branch -D pr-<PR>-verify 2>/dev/null || trueIf still behind main, repeat steps 2 through 9.
- Write prep summary artifacts (Mandatory)
Update .local/prep.md with:
- Current HEAD sha from
git rev-parse HEAD. - Short bullet list of changes.
- Gate results.
- Push confirmation.
- Rebase verification result.
Create or overwrite .local/prep.md and verify it exists and is non-empty:
git rev-parse HEAD
ls -la .local/prep.md
wc -l .local/prep.md- Output
Include a diff stat summary:
git diff --stat origin/main..HEAD
git diff --shortstat origin/main..HEADReport totals: X files changed, Y insertions(+), Z deletions(-).
If gates passed and push succeeded, print exactly:
PR is ready for /mergeprOtherwise, list remaining failures and stop.
Guardrails
- Worktree only.
- Do not delete the worktree on success.
/mergeprmay reuse it. - Do not run
gh pr merge. - Never push to main. Only push to the PR head branch.
- Run and pass all gates before pushing.
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- neul-labs/openclawMU★ 3330% same
Wrote their own version · 11
- mengxi-ream/read-frog★ 10ksame name
- chattymin/PokeTokenBar★ 532same name
- WikiEducationFoundation/WikiEduDashboard★ 430same name
- NVIDIA/NeMo-Relay★ 224same name
- atsushi-green/ds-ai-coding-skills★ 86same name
- NVIDIA/NeMo-Fabric★ 64same name
- dativo-io/talon★ 17same name
- pnnl/adept-agentic★ 2same name
- andreilupu/my-claude-skills★ 1same name
- briansu2004/MyAgentSkills★ 1same name
1 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 repository86 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- merge-prSkill
- review-prSkill
- 1passwordSkill
- aave-bscSkill
- agentic-commerceSkill
- agent-identitySkill
- apple-notesSkill
- apple-remindersSkill
- bear-notesSkill
- binance-address-infoSkill
- binance-market-rankSkill
- binance-meme-rushSkill
- binance-spotSkill
- binance-token-auditSkill
- binance-token-infoSkill
- binance-trading-signalSkill
- birdSkill
- blogwatcherSkill
- blucliSkill
- bluebubblesSkill
- camsnapSkill
- canvasSkill
- clawhubSkill
- coding-agentSkill
- coingeckoSkill
- contract-deployerSkill
- debankSkill
- defi-dashboardSkill
- defillamaSkill
- discordSkill
- duneSkill
- eightctlSkill
- etherscanSkill
- four-memeSkill
- gas-trackerSkill
- geminiSkill
- gh-issuesSkill
- gifgrepSkill
- githubSkill
- gogSkill
- goplacesSkill
- healthcheckSkill
- himalayaSkill
- hyperliquidSkill
- imsgSkill
- macro-calendarSkill
- market-dataSkill
- mcporterSkill
- model-usageSkill
- nano-banana-proSkill
- nano-pdfSkill
- nft-managerSkill
- notionSkill
- obsidianSkill
- openai-image-genSkill
- openai-whisper-apiSkill
- openai-whisperSkill
- openhueSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

