skills.rest
xxrenzhe
xxrenzheCOMMUNITY
Explore all skills by this author →
GitHub

prepare-pr

Rebase GitHub pull requests onto main and apply review fixes.

Updated Aug 23, 2026
Search Tags:#automation#testing#ci/cd#github#rebase#pr
One-click install
npx skills add https://github.com/xxrenzhe/autobb --skill prepare-pr-xxrenzhe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/xxrenzhe/autobb/tree/main/openclaw/.agents/archive/prepare-pr-v1
Command: npx skills add https://github.com/xxrenzhe/autobb --skill prepare-pr-xxrenzhe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, rg, pnpm, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of preparing a GitHub Pull Request (PR) for merging by ensuring it's up-to-date, incorporates review feedback, and passes all automated checks.

Core Features & Use Cases

  • Rebase and Sync: Automatically rebases the PR branch onto the latest main branch.
  • Review Fixes: Integrates fixes for review comments marked as BLOCKER or IMPORTANT.
  • Gate Execution: Runs necessary build and test gates to ensure code quality.
  • Safe Pushing: Pushes changes exclusively to the PR's head branch, never to main.
  • Use Case: After receiving feedback on a PR, use this Skill to automatically apply the fixes, rebase your branch, run tests, and push the updated code, making it ready for the next review or merge.

Quick Start

Use the prepare-pr skill to get the pull request number 123 ready for merge.

Frequently Asked Questions about prepare-pr

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

FAQPage Schema
How do I automate rebase and test checks before merging a GitHub PR?▼

Automating GitHub PR preparation involves rebasing the PR branch onto main, running build and test gates, and pushing fixes exclusively to the head branch. This keeps the code clean, tested, and ready for integration.

Can I automatically resolve GitHub PR review comments marked as blockers?▼

Yes, PR review comments marked as BLOCKER or IMPORTANT can be automatically addressed. The automation applies fixes for these critical review findings, runs gates, and pushes the updated code to the PR head branch for the next review cycle.

Do I need gh and jq installed to automate pull request preparation?▼

Yes, automating PR preparation requires command-line tools including gh, jq, rg, and pnpm. These dependencies enable GitHub API interactions, JSON parsing, code searching, and running build and test gates within the CI/CD workflow.

What is the safest way to rebase a PR branch onto main without pushing to main?▼

Safe PR rebasing pushes changes exclusively to the PR's head branch and never directly to main. This approach rebases onto the latest main branch, executes automated gates, and commits fixes while protecting the main branch.

Why does my PR branch fail automated gates after addressing review feedback?▼

PR branches may fail automated gates if review fixes are applied without running build and test validations. Automating this process executes necessary gates after addressing review findings and rebasing, ensuring all checks pass before integration.

Related Skills

Explore More Software Engineering Skills→
NJUxljNJUxlj

session-logs

Search and analyze past conversation logs in JSONL format using jq and rg.

Community
Intermediate
phuetzphuetz
30

prepare-pr

Apply review fixes, run checks, and update GitHub PR head branches.

Community
Intermediate
danieldev24danieldev24

ci-cd-and-automation

Automates CI/CD pipeline setup and quality gates for code verification.

Community
Advanced
ZegocoverZegocover
1

zego-fix-merge-conflict

Automate merge conflict resolution in Git pull requests with interactive steps.

Official
Advanced