# Pr Create

> Prepare commits for the current feature branch, push, and create or update a PR to main.

- Skill: `anothersava/pr-create` (Agent Skill)
- Install (CLI): `npx skillmds@latest add anothersava/pr-create`
- Raw SKILL.md: https://api.skillmd.com/api/skills/anothersava/pr-create/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: AnotherSava (https://skillmd.com/u/anothersava)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/anothersava/pr-create

---


# Create PR for Plan-Based Changes

Prepare commits on the current feature branch, push, and create or update a PR to main.

Read `~/.claude/skills/shared/bash-rules.md` for bash command constraints.

## Context
- Repo root: !`git rev-parse --show-toplevel 2>/dev/null || pwd`
- Current branch: !`git rev-parse --abbrev-ref HEAD`
- Working tree status: !`git status --short`
- Commits ahead of main: !`git log main..HEAD --oneline`

## Working directory

`docs/plans/`, `.ralphex/progress/`, and any other file paths in this skill are relative to **Repo root** from Context. The cwd may be a subdirectory — prefix Repo root when calling Read/Glob/Grep/ls. Bare paths are cwd-relative and will silently miss plans and progress logs at the actual root.

## Workflow

### Step 1: Gather context

1. Use **Current branch** from context. If on `main`, abort — the user must check out the feature branch first.

2. Use **Working tree status** and **Commits ahead of main** from context. Abort if there are no commits ahead of main and no uncommitted changes.

3. Find the latest completed plan doc — look in `docs/plans/completed/` for the most recently created file whose name relates to the current branch or the work described in the commits.

4. Find the matching progress log in `.ralphex/progress/`.

5. Read the plan and progress log to understand the scope and intent of the changes.

### Step 2: Prepare commits

Reset commits back to the working tree and use `/commit` to create clean, atomic commits:

1. Run `/reset` — let the user choose which commits to reset.

2. Run `/commit`. It handles everything: diff analysis, atomic grouping, commit messages, import optimization, doc updates. Pass the plan doc and progress log context so it can write informed messages.

### Step 3: Rebase onto main

Ensure commits are based on the latest main so pr-merge can fast-forward:
```
git fetch origin main
git rebase main
```
If the rebase produces conflicts, stop and ask the user to resolve them.

### Step 4: Push and create/update PR

1. Push the branch. Use `--force-with-lease` if the remote branch already exists (commits were reset and recommitted):
   ```
   git push -u origin <branch-name> --force-with-lease
   ```
   For a new remote branch, a regular push works too — `--force-with-lease` is safe either way.

2. Draft the PR description. The PR body should be **more detailed than the commit message** — it is the primary review artifact. Build it from the plan doc, diff, and progress log:

   - **Overview**: 2-3 sentences on what this PR accomplishes and why (from the plan's Overview section)
   - **What changed**: bulleted list of concrete changes grouped by area (new modules, modified behavior, structural changes, test coverage). Derive from the diff, not just the plan — if the implementation added things not in the original plan, include them here.
   - **Design decisions**: key trade-offs and rationale (from plan's Design Notes). Highlight anything a reviewer should pay attention to.
   - **Scope reconciliation**: compare the plan against the actual diff. If the implementation diverged from the plan (added features, dropped features, changed approach), note the differences and why.
   - **Plan reference**: link to the plan document filename
   - **Test coverage**: summary of test files and what they cover

3. Check if a PR already exists for this branch: `gh pr view --json number,title,url`. If the command fails, no PR exists.

   **If no PR exists** — create one:
   ```
   gh pr create --base main --title "<title>" --body "<PR description>"
   ```

   **If a PR already exists** — update it with the new description:
   ```
   gh pr edit --title "<title>" --body "<PR description>"
   ```

4. Report the PR URL to the user.