prepare-pr

Automate GitHub Pull Request preparation by rebasing, fixing review findings, and running gates.

Updated Feb 8, 2026

Search Tags:#git #code review #CI/CD #GitHub #PR preparation

Ready to run

npx skills add https://github.com/dioerden/OpenClaw-Flash-Vault --skill prepare-pr-dioerden

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/dioerden/OpenClaw-Flash-Vault/tree/main/.agents/skills/prepare-pr
Command: npx skills add https://github.com/dioerden/OpenClaw-Flash-Vault --skill prepare-pr-dioerden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the preparation of GitHub Pull Requests (PRs) by handling rebasing, fixing review findings, running gates, and pushing changes to the PR head branch, reducing manual effort and potential errors.

Core Features & Use Cases

Automated PR Preparation: Handles the entire process of PR preparation, from rebasing onto the main branch to pushing the changes.
Review Finding Fixing: Applies fixes to BLOCKER and IMPORTANT review findings identified during the review process.
Gate Running: Executes gates to ensure the PR is ready for merging.
Use Case: After a PR has been reviewed and feedback has been provided, use this Skill to prepare the PR for merging, ensuring it meets all requirements.

Quick Start

Run the prepare-pr skill with the PR number or URL.

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 PR preparation and rebasing?▼

Automate GitHub PR preparation by using a script that handles rebasing onto the main branch, running automated checks, and pushing changes to the PR head branch. This reduces manual effort and potential errors in your software engineering workflow.

How do I fix code review findings before merging a pull request?▼

Fix code review findings before merging by applying automated fixes to BLOCKER and IMPORTANT review findings identified during the review process. This prepares your PR for final merging while ensuring it meets code quality requirements.

What is the best way to run CI/CD gates on a GitHub pull request?▼

Run CI/CD gates on a GitHub pull request by executing automated checks during the PR preparation phase. This ensures your code changes pass required quality gates and are fully ready for merging into the main branch.

Does automated PR preparation work with my existing GitHub workflow?▼

Automated PR preparation works with existing GitHub workflows by handling rebasing, review finding fixes, gate running, and pushing changes to the PR head branch. You simply run the process with your PR number or URL.

Why should I automate rebasing when preparing a pull request?▼

Automate rebasing when preparing a pull request to reduce manual effort and potential errors. It handles the entire process of updating your branch against the main branch, fixing review findings, and running gates before pushing changes.

What do I need to start preparing a GitHub PR for merging?▼

To start preparing a GitHub PR for merging, you need the PR number or URL. The automated process then handles rebasing, applies fixes to review findings, runs gates, and pushes changes to the PR head branch.