prepare-pr

Rebases GitHub PRs onto main branch and commits reviewed fixes with automated checks.

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

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 (PR) for merging by ensuring it's up-to-date, addresses review feedback, and passes all necessary checks.

Core Features & Use Cases

  • Rebase onto Main: Automatically rebases the PR branch onto the latest main branch to resolve conflicts.
  • Fix Review Findings: Addresses critical issues identified during code reviews.
  • Run Gates: Executes automated tests and build processes to ensure code quality.
  • Commit Fixes: Commits changes with a standardized format, including PR details and author attribution.
  • Push to Head Branch: Safely pushes the prepared changes back to the PR's head branch.

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 prepare a GitHub pull request for merging automatically?

Yes, the Skill fixes critical issues identified during code review. It addresses these review findings, runs automated build and test gates, and commits the changes with standardized formatting before pushing to the head branch.

Can I rebase my pull request branch onto the latest main branch using automation?

Yes, you can rebase your pull request branch onto the latest main branch using this automation. It resolves conflicts by rebasing the PR branch, ensuring your code integrates smoothly with the updated main branch.

Does this automation push prepared code changes directly to the main branch?

No, this automation does not push directly to the main branch. It safely pushes the prepared changes back to the PR's head branch, maintaining repository integrity while ensuring the pull request is ready for merging.

What's the best way to ensure my pull request passes CI/CD gates before merging?

The best way to ensure a pull request passes CI/CD gates is to run automated tests and build processes. This Skill executes these gates, commits fixes, and guarantees the PR is mergeable without manual intervention.

Why should I automate pull request preparation instead of resolving conflicts manually?

Automating pull request preparation eliminates manual conflict resolution and review fixes. It standardizes commit formatting with PR details and author attribution while guaranteeing the branch is mergeable, saving development time.