skills.rest
badbsallyy
badbsallyyCOMMUNITY
Explore all skills by this author →
GitHub

prepare-pr

Rebase a GitHub pull request onto main and run automated checks.

Updated Feb 15, 2026
Search Tags:#automation#git#code review#pull request#github#rebase
One-click install
npx skills add https://github.com/badbsallyy/openclaw-source-code --skill prepare-pr-badbsallyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/badbsallyy/openclaw-source-code/tree/main/openclaw-sourcecode.zip/.agents/skills/prepare-pr
Command: npx skills add https://github.com/badbsallyy/openclaw-source-code --skill prepare-pr-badbsallyy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of getting a GitHub Pull Request ready to be merged by handling rebasing, fixing review comments, and running automated checks.

Core Features & Use Cases

  • Automated Rebasing: Integrates the latest changes from the main branch into your PR branch.
  • Review Fixes: Addresses comments and issues identified during code review.
  • Gate Execution: Runs automated tests and build processes to ensure code quality.
  • Use Case: After receiving feedback on a PR, use this Skill to automatically apply the fixes, rebase your branch, and ensure all tests pass before merging.

Quick Start

Use the prepare-pr skill to get the pull request number 123 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 GitHub pull request and fix code review comments before merging?▼

To automatically rebase a GitHub pull request and fix code review comments, you can use an automation skill that rebases onto the main branch, addresses review findings, and commits fixes. This process ensures your branch is up-to-date and passes automated gates before merge.

What is the best way to ensure a pull request passes all automated tests before merge?▼

The best way to ensure a pull request passes automated tests is to execute automated gates that run build processes and test suites. This verifies code quality and confirms all checks pass before the branch is merged into the main pipeline.

How does automated rebasing integrate the latest changes from the main branch into a PR?▼

Automated rebasing integrates the latest changes from the main branch by resetting your PR head branch onto the current main branch tip. This replays your commits over the latest codebase, resolving divergent histories and ensuring your pull request is ready for merge.

Can I use scripts to push automated fixes to a PR head branch after addressing review findings?▼

Yes, you can use scripts to push automated fixes to a PR head branch after addressing review findings. The scripts commit the applied fixes and push them directly to the remote pull request branch, ensuring all review comments are resolved and synced.

What should I do if my pull request is not up-to-date and failing automated gate checks?▼

If your pull request is failing automated gate checks and not up-to-date, you need to execute a preparation workflow that rebases onto main, addresses review findings, and runs automated gates. This sequence commits fixes and pushes to the PR head branch to clear failing checks.

Related Skills

Explore More Software Engineering Skills→
wyattjohwyattjoh
1

pr-status

Visualize GitHub pull request stacks and identify stale local branches.

Community
Intermediate
takemi-ohamatakemi-ohama

merged

Update the main branch and delete the merged feature branch after a PR merge.

Community
Advanced
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
assertchrisassertchris
2

custom-conflict-resolution

Resolve Git merge conflicts file by file using a rebase strategy.

Community
Advanced