Rebase PR commits onto origin/main and push prepared changes to the PR head.
npx skills add https://github.com/carlooss-pm/agents --skill prepare-pr-carlooss-pm
Please help me install this Agent Skill. Skill: prepare-pr Source: https://github.com/carlooss-pm/agents/tree/main/projects/openclaw/skills/prepare-pr Command: npx skills add https://github.com/carlooss-pm/agents --skill prepare-pr-carlooss-pm
This workflow automates the end-to-end preparation of a GitHub PR for merge by rebasing onto main, applying review findings, running gates, and pushing updated commits to the PR head, while never touching main.
After opening a PR, run the prepare-pr workflow to rebase onto origin/main, fix blockers from local review, run gates, commit prep changes, and push to the PR head.
High-intent search queries and answers about installing and using this skill.
Preparing a pull request for merge involves rebasing PR commits onto origin/main, applying local review fixes, running required gates, and pushing updated commits to the PR head. This process ensures a clean, merge-ready branch while never touching the main branch.
The best way to rebase commits and run gates before merging is to automate the end-to-end PR preparation: rebase onto origin/main, apply fixes from local review, run build and lint tests, commit prep changes, and push safely to the PR head.
Applying local review fixes during PR preparation works by reading blockers from a .local/review.md file, updating related docs or changelogs if flagged, and committing these prep changes to the PR head to ensure the pull request is polished and merge-ready.
Yes, you can push prep changes to the PR head without touching the main branch. The workflow uses a safe push strategy to update the PR head and verifies the PR is not behind main, ensuring origin/main remains untouched throughout the preparation.
Your pull request may fail gates after rebasing onto origin/main if the updated commits introduce build, lint, or test conflicts. The preparation workflow runs these required gates to verify readiness and prevents signaling for merge if blockers remain unresolved.
Yes, a local review file is needed to apply fixes from local review during PR preparation. The workflow reads .local/review.md to identify blockers, apply necessary updates to docs or changelogs, and ensure all issues are resolved before running gates.
Suntory-N-WaterAutomate GitHub PR reviews with diff analysis and comment operations via GitHub CLI.
cooopmacVerify tests and merge branches or create pull requests.
fabiano001Run Codex CLI peer reviews on GitHub PRs and generate Markdown reports.
gewoonsebaRebase the current branch onto origin/main after conflict resolution.
