prepare-pr

Rebase GitHub pull requests onto main, apply review fixes, run checks, and push.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/sky770825/openclaw-console-hub --skill prepare-pr-sky770825
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/sky770825/openclaw-console-hub/tree/main/openclaw-main/.agents/skills/prepare-pr
Command: npx skills add https://github.com/sky770825/openclaw-console-hub --skill prepare-pr-sky770825

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of preparing a GitHub Pull Request for merging by addressing review feedback, ensuring all automated checks pass, and updating the branch.

Core Features & Use Cases

  • Automated Rebasing: Rebase your PR branch onto the latest main branch to resolve conflicts.
  • Review Fixes: Apply changes based on feedback from code reviews.
  • Gate Execution: Run automated checks (linting, testing, builds) to ensure code quality.
  • Commit & Push: Commit your fixes and push the updated branch back to the PR.
  • Use Case: After receiving feedback on a PR, you can use this Skill to automatically incorporate the suggestions, rebase your branch, run all tests, and push the updated code, making it ready for the next review or merge.

Quick Start

Use the prepare-pr skill to rebase the current PR onto main, fix review findings, run gates, commit fixes, and push to the PR head branch.

Frequently Asked Questions about prepare-pr

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

FAQPage Schema
How do I automate GitHub pull request preparation for merge?

Automate GitHub pull request preparation by rebasing onto the main branch, addressing review findings, running automated gates, committing fixes, and pushing to the PR head branch. This ensures the PR is conflict-free and passes all checks before merge.

What is the best way to rebase a PR branch and resolve merge conflicts automatically?

The best way to rebase a PR branch and resolve conflicts is using an automated preparation workflow that rebases onto the latest main branch, applies review fixes, and executes automated checks to ensure the branch is conflict-free for merging.

Can I automatically apply code review feedback and run CI/CD gates on a PR?

Yes, you can automatically apply code review feedback and run CI/CD gates. The workflow addresses review findings, executes automated checks like linting and testing, commits the fixes, and pushes the updated code to the PR head branch.

Does automated PR preparation work with my existing GitHub CI/CD pipeline?

Automated PR preparation works with your existing GitHub CI/CD pipeline by executing automated gates such as linting, testing, and builds. It ensures all configured checks pass before committing fixes and pushing the updated branch.

Why does my pull request have merge conflicts after addressing review findings?

Pull requests develop merge conflicts after review fixes because the main branch has advanced. Automated PR preparation resolves this by rebasing your branch onto the latest main branch before applying fixes and running checks.