skills.rest
adoresever
adoreseverCOMMUNITY
Explore all skills by this author →
GitHub

prepare-pr

Rebase pull requests onto origin/main, apply review fixes, and push to the PR head.

202|36|Updated Jan 27, 2026
Search Tags:#automation#git#rebase#pr#gates#pull-request#review-fixes
One-click install
npx skills add https://github.com/adoresever/AGI_Ananas --skill prepare-pr-adoresever
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/adoresever/AGI_Ananas/tree/main/26.2.21openclaw-viking/.agents/archive/prepare-pr-v1
Command: npx skills add https://github.com/adoresever/AGI_Ananas --skill prepare-pr-adoresever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare-pr automates the complex, error-prone process of preparing a PR for merge by rebasing onto main, applying review fixes, running gates, committing fixes, and pushing to the PR head branch, while never pushing to main.

Core Features & Use Cases

  • Rebase PR commits onto origin/main to ensure a clean base for merge.
  • Apply review findings, address blockers, and perform required gates before merging.
  • Generate deterministic handoff artifacts and push updates to the PR head for seamless collaboration.

Quick Start

Provide the PR number or URL to begin the prep workflow.

Frequently Asked Questions about prepare-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a pull request for merge after resolving code review fixes?▼

Preparing a pull request for merge involves rebasing commits onto origin/main, applying review fixes, and running required gates. This process ensures blockers are resolved and the PR head is ready for a seamless merge.

What is the safest way to rebase commits onto main before merging a PR?▼

The safest rebase approach enforces strict safety constraints, such as never pushing directly to main. It requires explicit remote handling and verification before pushing updates to the PR head branch.

How do I automate applying review fixes and passing required gates before a GitHub merge?▼

Automating PR preparation applies review findings, addresses blockers, and runs required gates automatically. It then commits the fixes and pushes the updated PR head for collaboration.

Can I automatically rebase a PR onto origin/main without pushing to main?▼

Yes, automated PR preparation rebases onto origin/main while enforcing safety constraints that never push to main. It requires explicit remote handling and verification before pushing to the PR branch.

What are the limitations of automating pull request merge preparation?▼

Limitations include the strict requirement for explicit remote handling and verification before pushing updates. The automation enforces safety constraints like never pushing to main, requiring blockers to be fully resolved before merge.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

code-review

Review branch diffs and produce a severity-tagged findings table.

Official
Intermediate
kamp-uskamp-us
25

ship-it

Automate squash merging of verified Pull Requests with green CI status.

Official
Advanced
xxihxxih
1

laravel-verification

Verify Laravel projects for configuration, code quality, testing, security, and deployment readiness.

Community
Advanced
facebookfacebook
11.2k

non-interactive-git-rebase

Script Git interactive rebases using GIT_SEQUENCE_EDITOR and --exec.

Official
Advanced