prepare-pr

Rebase GitHub Pull Requests onto main and run automated gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of getting a GitHub Pull Request ready for merging by automating essential pre-merge checks and updates.

Core Features & Use Cases

  • Automated Rebasing: Rebase PR commits onto the latest main branch to resolve conflicts.
  • Review Fixes: Apply fixes for review findings documented in .local/review.md.
  • Gate Execution: Run automated tests and build processes to ensure code quality.
  • Use Case: After receiving feedback on a PR, use this Skill to automatically rebase, fix reported issues, ensure all tests pass, and push the updated branch, making it ready for a final review or merge.

Quick Start

Use the prepare-pr skill to rebase the current PR onto main and run all required gates.

Frequently Asked Questions about prepare-pr

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

FAQPage Schema
How do I prepare a GitHub pull request for merge by rebasing onto main?

To prepare a pull request for merge, you can automate rebasing commits onto the latest main branch, execute automated gates, and push the updated head branch to ensure the PR is merge-ready.

Can I automate code review fixes and run CI/CD gates before merging a PR?

Yes, you can automate code review fixes by applying changes documented in a local review file, executing CI/CD automated gates to verify quality, and committing the fixes directly to the PR branch.

What is the best way to resolve GitHub PR conflicts and ensure tests pass automatically?

The best way to resolve PR conflicts and ensure tests pass is to automatically rebase onto the main branch, execute required automated gates for build verification, and push the resolved commits.

Does this PR preparation process execute the actual merge on GitHub?

No, the PR preparation process does not execute the actual merge on GitHub; it strictly automates the pre-merge steps like rebasing, fixing review findings, and running gates to make the branch ready.

How do I apply review findings from a markdown file to my Git pull request branch?

You can apply review findings to your Git pull request branch by reading the documented fixes from a local markdown file, committing the necessary changes, and pushing them to the PR head branch.