skills.rest
TermiX-official
TermiX-officialOFFICIAL
Explore all skills by this author →
Website𝕏@termix_aiGitHub

prepare-pr

Rebase GitHub pull requests onto main and push prepared changes.

109|11|Updated Feb 6, 2026
Search Tags:#git#worktree#merge#rebase#pr#pull-request
One-click install
npx skills add https://github.com/TermiX-official/cryptoclaw --skill prepare-pr-termix-official
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/TermiX-official/cryptoclaw/tree/main/.agents/skills/prepare-pr
Command: npx skills add https://github.com/TermiX-official/cryptoclaw --skill prepare-pr-termix-official

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers prepare GitHub pull requests for merge by automatically rebasing, applying review fixes, running required gates, and updating the PR head branch without touching main.

Core Features & Use Cases

  • PR rebase & fix integration: Rebase the PR against origin/main, incorporate review findings, and ensure conflicts are resolved before merge.
  • Gate enforcement & prep artifacts: Run required gates, generate a prep summary file, and push prepared changes to the PR head.
  • Use Case: A maintainer uses this skill after /reviewpr to prep a PR for merge with a clean head, up-to-date base, and documented prep steps.

Quick Start

Use the prepare-pr skill to start the PR prep workflow on a repository you own.

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 a clean merge?▼

To prepare a GitHub pull request for a clean merge, you rebase the head branch onto origin/main, resolve conflicts, apply review findings, run required gate checks, and push the updated branch.

What is the best way to rebase a pull request onto main without touching the main branch?▼

Rebasing a pull request onto main without touching main is best done within an isolated git worktree workflow that orchestrates PR metadata retrieval, applies review fixes, and safely pushes only the updated head branch.

How do I integrate code review findings and run gates before merging a PR?▼

Integrating code review findings and running gates before merging a PR involves applying review fixes, executing required gate checks within a worktree, generating a prep summary, and pushing the prepared changes to the head branch.

Do I need the GitHub CLI and git worktree to automate pull request preparation?▼

Yes, automating pull request preparation requires the Git and GitHub CLI tools within a worktree workflow to fetch PR metadata, enforce safety constraints against pushing to main, and generate prep artifacts.

What are the limitations or safety constraints when preparing a PR for merge?▼

A key safety constraint when preparing a PR for merge is that the workflow never pushes directly to main, restricting write operations to the PR head branch to preserve repository integrity and prevent accidental base branch updates.

Can I generate a prep summary artifact after addressing pull request review comments?▼

Yes, you can generate a prep summary artifact after addressing pull request review comments by running required gates, applying fixes, and writing a documented summary file that guides users through each completed prep step.

Related Skills

Explore More Software Engineering Skills→
kagentikagenti
292

git:status

Aggregate Git worktree status, pull request details, and TODO file summaries.

Official
Intermediate
electroheadfxelectroheadfx
4

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
sehoon787sehoon787
16

laravel-verification

Run environment checks, linting, tests, security audits, and migration verification for Laravel projects.

Community
Advanced
bmsull560bmsull560

jr-rebase

Resolves git rebase conflicts in feature branches via guided marker resolution.

Community
Intermediate