skills.rest
jonnytacos8
jonnytacos8COMMUNITY
Explore all skills by this author →
GitHub

prepare-pr

Rebase GitHub PRs onto main, apply review fixes, run gates, and prepare handoff artifacts.

Updated Feb 13, 2026
Search Tags:#automation#git#rebase#pr#ci#pull-request
One-click install
npx skills add https://github.com/jonnytacos8/closed_claw --skill prepare-pr-jonnytacos8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/jonnytacos8/closed_claw/tree/main/.agents/archive/prepare-pr-v1
Command: npx skills add https://github.com/jonnytacos8/closed_claw --skill prepare-pr-jonnytacos8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare PR head branch for merge with review fixes, green gates, and deterministic merge handoff artifacts. It ensures that main remains untouched and PRs are ready for review.

Core Features & Use Cases

  • Rebase PR onto origin/main and resolve conflicts deterministically.
  • Apply review findings by implementing fixes on the PR branch.
  • Run required gates, commit prep changes, and prepare handoff artifacts for the PR head.
  • Ensure safe pushes only to the PR head and never to main.

Quick Start

Rebase the PR onto main, fix review findings, run gates, commit fixes, and push updates to the PR head without touching main.

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 rebase the PR head branch onto origin/main, resolve conflicts deterministically, apply review fixes, and run required gates. This ensures the branch is updated and ready for safe, auditable merging.

What is the safest way to apply review fixes and run CI gates before merging a PR?▼

The safest way to apply fixes is implementing them directly on the PR branch, running required CI gates, and committing prep changes. This workflow strictly enforces never pushing to main and only updating the PR head.

Can I automate multi-PR reviews and still ensure main remains untouched?▼

Yes, you can automate multi-PR reviews by preparing deterministic handoff artifacts for each PR head. The process enforces strict guardrails that always update the PR head branch and never push directly to main.

How do I resolve git conflicts deterministically when rebasing a pull request?▼

You resolve git conflicts deterministically during a pull request rebase by automating the conflict resolution logic on the PR branch. This updates the PR head while preserving the main branch and producing auditable prep artifacts.

What are deterministic merge handoff artifacts in GitHub PR automation?▼

Deterministic merge handoff artifacts are auditable outputs generated after rebasing a PR, applying fixes, and running gates. They ensure safe, coordinated multi-PR reviews by providing a consistent state for final merging.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

worktree-sync

Syncs Git worktrees by fetching remote and rebasing or merging main into feature branches.

Community
Basic
TeamSloppyTeamSloppy
26

github-pr-workflow

Automate GitHub PR workflows with branches, commits, and merges via gh and the GitHub API.

Official
Advanced
sky770825sky770825

prepare-pr

Rebase GitHub pull requests onto main, apply review fixes, run checks, and push.

Community
Advanced
alo-expalo-exp
6

finishing-branch

Finalize Git branches by verifying tests, choosing merge strategies, and creating PRs.

Official
Intermediate