skills.rest
lalomorales22
lalomorales22COMMUNITY
Explore all skills by this author →
Website𝕏@lalopenguinGitHub

prepare-pr

Rebases GitHub PRs onto main and applies review fixes before pushing to head branch.

Updated Aug 23, 2026
Search Tags:#automation#git#merge#review#pull-request#prepare-pr
One-click install
npx skills add https://github.com/lalomorales22/penguins --skill prepare-pr-lalomorales22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-pr
Source: https://github.com/lalomorales22/penguins/tree/main/.agents/archive/prepare-pr-v1
Command: npx skills add https://github.com/lalomorales22/penguins --skill prepare-pr-lalomorales22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile PR branches with the mainline by rebasing, applying review fixes, and enforcing gate checks to streamline merge readiness and reduce manual toil.

Core Features & Use Cases

  • Rebase PR head onto origin/main to ensure an up-to-date base before merge.
  • Automatically apply review fixes, resolve blockers, and execute required gates to validate readiness.
  • Output deterministic handoff artifacts (.local/prep.md and .local/prep.env) for auditing and handoff.

Quick Start

Run the prepare-pr workflow to rebase a PR, fix review findings, run gates, commit fixes, and push to the PR head.

Frequently Asked Questions about prepare-pr

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

FAQPage Schema
How do I automate rebasing a pull request onto main before merge?▼

Automating pull request rebasing onto main resolves branch conflicts and updates the base before merge. This Skill rebases the PR head onto origin/main, applies review fixes, and runs gated checks to validate readiness.

How do I automatically resolve GitHub PR review findings and blockers?▼

Resolving GitHub PR review findings automatically requires applying fixes and executing required gates. This Skill addresses review blockers, commits the necessary fixes, and pushes only to the PR head branch.

What is the best way to ensure deterministic merge readiness for pull requests?▼

Deterministic merge readiness for pull requests means enforcing safety rules and validating checks before integration. This Skill rebases onto main, executes required gates, and emits deterministic handoff artifacts for auditing.

Does this PR preparation workflow push changes directly to the main branch?▼

PR preparation workflow changes are not pushed directly to the main branch. This Skill enforces safety rules by committing fixes and pushing only to the PR head branch to maintain mainline stability.

Can I generate audit artifacts when preparing a GitHub PR for merge?▼

Generating audit artifacts when preparing a GitHub PR provides traceability for merge readiness. This Skill outputs deterministic handoff artifacts, specifically .local/prep.md and .local/prep.env files, for auditing purposes.

Related Skills

Explore More Software Engineering Skills→
Positronic-RoboticsPositronic-Robotics
84

push-pr

Push the current branch to origin and create a PR to upstream.

Official
Intermediate
takemi-ohamatakemi-ohama

merged

Update the main branch and delete the merged feature branch after a PR merge.

Community
Advanced
baphledbaphled
1

check-compliance

Run linting, formatting, security scans, and tests before committing code.

Community
Intermediate
JacobPEvansJacobPEvans
3

troubleshoot-rebase

Diagnose Git rebase failures and recover from merge conflicts.

Community
Advanced