How do I install the Prepare Pr skill?

Run npx skillmds@latest add adoresever/prepare-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Prepare Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Prepare Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Prepare Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Prepare Pr?

adoresever (@adoresever) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Prepare Pr by adoresever — Agent Skill

Name: Prepare Pr
Author: adoresever

File contents

Prepare PR

Overview

Prepare the PR head branch for merge after /review-pr.

Inputs

Ask for PR number or URL.
If missing, use .local/pr-meta.env if present in the PR worktree.

Safety

Never push to main.
Only push to PR head with explicit --force-with-lease against known head SHA.
Do not run git clean -fdx.
Wrappers are cwd-agnostic; run from repo root or PR worktree.

Execution Contract

Run setup:

scripts/pr-prepare init <PR>

Resolve findings from structured review:

.local/review.json is mandatory.
Resolve all BLOCKER and IMPORTANT items.

Commit scoped changes with concise subjects (no PR number/thanks; those belong on the final merge/squash commit).
Run gates via wrapper.
Push via wrapper (includes pre-push remote verification, one automatic lease-retry path, and post-push API propagation retry).

Optional one-shot path:

scripts/pr-prepare run <PR>

Steps

Setup and artifacts

scripts/pr-prepare init <PR>

ls -la .local/review.md .local/review.json .local/pr-meta.env .local/prep-context.env
jq . .local/review.json >/dev/null

Resolve required findings

List required items:

jq -r '.findings[] | select(.severity=="BLOCKER" or .severity=="IMPORTANT") | "- [\(.severity)] \(.id): \(.title) => \(.fix)"' .local/review.json

Fix all required findings. Keep scope tight.

Update changelog/docs (changelog is mandatory in this workflow)

jq -r '.changelog' .local/review.json
jq -r '.docs' .local/review.json

Changelog gate requirement:

CHANGELOG.md must include a newly added changelog entry line.
When PR author metadata is available, that same changelog entry line must include (#<PR>) thanks @<pr-author>.

Commit scoped changes

Use concise, action-oriented subject lines without PR numbers/thanks. The final merge/squash commit is the only place we include PR numbers and contributor thanks.

Use explicit file list:

scripts/committer "fix: <summary>" <file1> <file2> ...

Run gates

scripts/pr-prepare gates <PR>

Push safely to PR head

scripts/pr-prepare push <PR>

This push step includes:

robust fork remote resolution from owner/name,
pre-push remote SHA verification,
one automatic rebase + gate rerun + retry if lease push fails,
post-push PR-head propagation retry,
idempotent behavior when local prep HEAD is already on the PR head,
post-push SHA verification and .local/prep.env generation.

Verify handoff artifacts

ls -la .local/prep.md .local/prep.env

Output

Summarize resolved findings and gate results.
Print exactly: PR is ready for /merge-pr.

Guardrails

Do not run gh pr merge in this skill.
Do not delete worktree.

---name: prepare-prdescription: Script-first PR preparation with structured findings resolution, deterministic push safety, and explicit gate execution.---# Prepare PR## OverviewPrepare the PR head branch for merge after `/review-pr`.## Inputs- Ask for PR number or URL.- If missing, use `.local/pr-meta.env` if present in the PR worktree.## Safety- Never push to `main`.- Only push to PR head with explicit `--force-with-lease` against known head SHA.- Do not run `git clean -fdx`.- Wrappers are cwd-agnostic; run from repo root or PR worktree.## Execution Contract1. Run setup:```shscripts/pr-prepare init <PR>```2. Resolve findings from structured review:- `.local/review.json` is mandatory.- Resolve all `BLOCKER` and `IMPORTANT` items.3. Commit scoped changes with concise subjects (no PR number/thanks; those belong on the final merge/squash commit).4. Run gates via wrapper.5. Push via wrapper (includes pre-push remote verification, one automatic lease-retry path, and post-push API propagation retry).Optional one-shot path:```shscripts/pr-prepare run <PR>```## Steps1. Setup and artifacts```shscripts/pr-prepare init <PR>ls -la .local/review.md .local/review.json .local/pr-meta.env .local/prep-context.envjq . .local/review.json >/dev/null```2. Resolve required findingsList required items:```shjq -r '.findings[] | select(.severity=="BLOCKER" or .severity=="IMPORTANT") | "- [\(.severity)] \(.id): \(.title) => \(.fix)"' .local/review.json```Fix all required findings. Keep scope tight.3. Update changelog/docs (changelog is mandatory in this workflow)```shjq -r '.changelog' .local/review.jsonjq -r '.docs' .local/review.json```Changelog gate requirement:- `CHANGELOG.md` must include a newly added changelog entry line.- When PR author metadata is available, that same changelog entry line must include `(#<PR>) thanks @<pr-author>`.4. Commit scoped changesUse concise, action-oriented subject lines without PR numbers/thanks. The final merge/squash commit is the only place we include PR numbers and contributor thanks.Use explicit file list:```shscripts/committer "fix: <summary>" <file1> <file2> ...```5. Run gates```shscripts/pr-prepare gates <PR>```6. Push safely to PR head```shscripts/pr-prepare push <PR>```This push step includes:- robust fork remote resolution from owner/name,- pre-push remote SHA verification,- one automatic rebase + gate rerun + retry if lease push fails,- post-push PR-head propagation retry,- idempotent behavior when local prep HEAD is already on the PR head,- post-push SHA verification and `.local/prep.env` generation.7. Verify handoff artifacts```shls -la .local/prep.md .local/prep.env```8. Output- Summarize resolved findings and gate results.- Print exactly: `PR is ready for /merge-pr`.## Guardrails- Do not run `gh pr merge` in this skill.- Do not delete worktree.

Frequently asked questions

Prepare Pr