skills.rest
Clawdi-AI
Clawdi-AIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

prepare-pr

Rebase GitHub PRs onto main, apply review fixes, and run tests.

4|2|Updated Feb 26, 2026
Search Tags:#automation#ci/cd#code review#pull request#github#rebase
One-click install
npx skills add https://github.com/Clawdi-AI/openclaw --skill prepare-pr-clawdi-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/Clawdi-AI/openclaw/tree/main/.agents/archive/prepare-pr-v1
Command: npx skills add https://github.com/Clawdi-AI/openclaw --skill prepare-pr-clawdi-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of getting a GitHub Pull Request ready for merging by handling rebasing, fixing review comments, and running necessary checks.

Core Features & Use Cases

  • Automated Rebasing: Rebase the PR branch onto the latest main branch to resolve conflicts.
  • Review Fix Integration: Apply fixes for review findings marked as BLOCKER or IMPORTANT.
  • Gate Execution: Run automated tests and checks to ensure code quality and stability.
  • Safe Pushing: Push changes back to the PR's head branch securely.
  • Use Case: After receiving feedback on a PR, use this Skill to automatically update the branch, address comments, pass all tests, and prepare it for a seamless merge.

Quick Start

Use the prepare-pr skill to get the current pull request ready for merging.

Frequently Asked Questions about prepare-pr

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

FAQPage Schema
How do I automatically rebase a pull request and resolve conflicts before merging?▼

Automatically rebase a pull request by rebasing the PR branch onto the latest main branch to resolve conflicts. This ensures the branch is up to date and conflict-free before merging.

Can I automatically fix GitHub code review comments on a pull request branch?▼

Yes, you can fix GitHub code review comments by applying fixes for review findings marked as BLOCKER or IMPORTANT. This integrates review feedback directly into the branch updates.

What's the best way to run automated tests and gates on a PR branch before pushing?▼

Run automated tests and gates by executing quality checks on the rebased branch. This ensures code stability and verifies that the pull request meets quality standards before pushing.

Do I need the GitHub CLI and pnpm to automate pull request preparation?▼

Yes, you need the GitHub CLI, Git, and pnpm installed. These dependencies are required for execution, repository interaction, and dependency management during the pull request preparation process.

Why does my pull request branch fail automated checks after rebasing onto main?▼

A pull request branch may fail automated checks if gate execution detects quality issues or unresolved conflicts. The process runs tests to ensure stability, requiring all checks to pass before pushing.

Related Skills

Explore More Software Engineering Skills→
jandragsbaekjandragsbaek
1

create-pr

Create feature branches, rebase onto main, and open GitHub PRs with labels.

Community
Intermediate
tunneleventunneleven

c4flow:merge

Merge pull requests into the main branch with pre-merge checks and post-merge cleanup.

Community
Intermediate
s3nex-coms3nex-com

pr-merge-orchestrator

Coordinate pull request lifecycle from review through merge with mandatory gates.

Community
Advanced
hypeJunctionhypeJunction
1

iterate-pr

Iterate on open pull requests to resolve CI failures and review feedback.

Community
Advanced