prepare-pr

Rebase GitHub pull requests onto main, fix review issues, and run build and test gates.

55|6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/NJX-njx/opensoul --skill prepare-pr-njx-njx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/NJX-njx/opensoul/tree/main/.agents/skills/prepare-pr
Command: npx skills add https://github.com/NJX-njx/opensoul --skill prepare-pr-njx-njx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of preparing a GitHub pull request for merging by rebasing onto the latest main branch, fixing review findings, and pushing updates, reducing manual effort and errors.

Core Features & Use Cases

  • Automated Rebase: Rebase PR commits onto the current main branch to ensure up-to-date code integration.
  • Review Findings Fixing: Address blockers and important issues from review reports within the codebase.
  • Full Gates Execution: Run comprehensive checks including build, tests, and validations to certify readiness for merging.
  • Push and Verify: Force push changes to the PR branch and verify it is not behind main, preparing the PR for final merge.

Quick Start

Initiate the preparation process by running the automation to rebase your PR, fix issues, and push updates for review and 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 onto the main branch?

Automating a pull request rebase onto main involves updating your PR branch with the latest commits, running build gates, and force pushing the changes. This Skill scripts that sequence to ensure smooth integration without manual git commands.

What is the best way to fix code review findings and push updates to a PR branch?

Fixing code review findings and pushing updates requires addressing blockers in the codebase, running validations, and force pushing the corrected commits. This process updates the PR branch automatically to certify readiness for merging.

Can I run continuous integration gates before pushing rebased commits to GitHub?

Yes, running continuous integration gates before pushing is supported. The Skill executes comprehensive build, test, and validation checks after rebasing and fixing issues, ensuring code correctness before updating the remote PR branch.

How do I verify a GitHub PR branch is not behind main before merging?

To verify a PR branch is not behind main, you rebase onto the latest main branch and check the commit history. This Skill performs the rebase and push operations, verifying the branch alignment to facilitate a smooth merge.

Does this automated rebase workflow require manual git conflict resolution?

Automated rebase workflows handle the git operations, but complex conflicts may still require manual intervention. This Skill focuses on automating the rebase, fixing review issues, and running gates, reducing manual effort for straightforward integrations.

Why should I automate pull request preparation instead of rebasing manually?

Automating pull request preparation reduces manual effort and errors by scripting the rebase, review finding fixes, and gate executions. It ensures the PR branch is updated and validated against main, facilitating a smoother merging workflow.