prepare-pr_skill

Overview

This skill prepares a pull request head branch for merge using a script-first, deterministic workflow that enforces structured findings resolution and safe push behavior. It ensures required findings are resolved, scoped commits are created, gates are executed, and the PR head is pushed with lease and verification safeguards. The output is a clear handoff confirming the PR is ready for merge.

How this skill works

The skill initializes a PR prep session, validates required artifacts, and enumerates BLOCKER and IMPORTANT findings from the structured review file. You resolve findings, update changelog/docs, and create focused commits via the committer wrapper. Gates run through the wrapper, and the push step performs pre-push SHA checks, a lease-safe force-push path with an automated rebase+retry, and post-push propagation verification, producing local handoff artifacts.

When to use it

• After /review-pr has produced .local/review.json for a PR
• When you must resolve all BLOCKER and IMPORTANT review findings before merging
• When you need deterministic, lease-safe pushes to a PR head branch
• When changelog or docs updates are required as part of PR preparation
• When you want an auditable handoff and explicit gate execution before merge

Best practices

• Run scripts/pr-prepare init <PR> from the repository root or PR worktree to gather artifacts
• Keep fix commits tightly scoped and use concise, action-oriented commit subjects (no PR numbers/thanks)
• Always fix all BLOCKER and IMPORTANT findings listed in .local/review.json before proceeding
• Use the provided committer wrapper with an explicit file list to avoid accidental changes
• Rely on the wrapper for gates and push; never push directly to main and avoid destructive git clean commands

Example use cases

• Prepare a contributor's PR for merge after an AI-assisted review identified critical issues
• Enforce a release process that requires changelog entries and docs updates as part of PR prep
• Safely force-update a PR head after a targeted rebase while ensuring remote SHA verification
• Produce .local/prep.md and .local/prep.env artifacts for CI or release automation handoff
• Run a one-shot prep flow with scripts/pr-prepare run <PR> for small, well-scoped fixes