skills.rest
SeanHogg
SeanHoggCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prepare-pr

Rebase a GitHub Pull Request onto main, fix review findings, run gates, and push.

3|1|Updated Feb 23, 2026
Search Tags:#automation#testing#code review#pull request#github#rebase
One-click install
npx skills add https://github.com/SeanHogg/coderClaw --skill prepare-pr-seanhogg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/SeanHogg/coderClaw/tree/main/.coderClaw/.agents/archive/prepare-pr-v1
Command: npx skills add https://github.com/SeanHogg/coderClaw --skill prepare-pr-seanhogg

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, ensuring it's up-to-date, fixes review findings, and passes all necessary checks.

Core Features & Use Cases

  • Rebasing: Automatically rebases the PR branch onto the latest main branch.
  • Issue Fixing: Addresses BLOCKER and IMPORTANT issues identified during code reviews.
  • Gate Execution: Runs build, check, and test gates to ensure code quality.
  • Safe Pushing: Pushes the prepared changes back to the PR's head branch securely.
  • Use Case: After receiving feedback on a PR, use this Skill to automatically apply the fixes, rebase your branch, run tests, and push the updated code, making it ready for the final merge.

Quick Start

Use the prepare-pr skill to get PR number 123 ready for merge.

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 automatically?▼

To prepare a GitHub pull request for merge, the Skill rebases the branch onto main, fixes review findings, runs automated gates, and securely pushes commits to the PR head branch, ensuring it is merge-ready without directly modifying main.

Can I automatically fix code review findings before merging a pull request?▼

Yes, you can automatically fix code review findings before merging a pull request by running the Skill, which identifies and addresses BLOCKER and IMPORTANT issues detected during the review process.

How do I rebase a pull request branch onto the latest main branch?▼

To rebase a pull request branch onto the latest main branch, the Skill automates the rebasing process, aligning your PR head branch with the current main branch before running build and test gates.

Does this Skill run automated build and test gates before pushing PR fixes?▼

Yes, the Skill runs automated build, check, and test gates to ensure code quality. After fixing review findings and rebasing, it verifies that all gates pass before securely pushing the prepared changes to the PR branch.

What is the safest way to push commits to a PR branch without merging to main?▼

The safest way to push commits without merging to main is using this Skill, which securely pushes prepared fixes to the PR's head branch only, deliberately avoiding direct merges or pushes to the main branch.

When should I avoid using automated pull request preparation?▼

You should avoid using automated pull request preparation when your repository lacks automated build or test gates, or when your code review findings require complex manual interventions that cannot be resolved by automated rebasing and fixing scripts.

Related Skills

Explore More Software Engineering Skills→
jkomorosjkomoros
9

land-branch

Rebase a feature branch onto main and merge via pull request.

Community
Intermediate
lachlanchenlachlanchen
1

prepare-pr

Rebase a GitHub pull request onto main, apply review fixes, run tests, and push.

Community
Advanced
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced
shonenmshonenm
2

conflict-resolve

Resolve Git merge and rebase conflicts by analyzing base, ours, and theirs states.

Community
Advanced