package-prlisted

# Package the Current Branch as a Pull Request The audience is a reviewer who wasn't there. They have twenty minutes, no context, and will approve or reject based on what this description tells them. The description is written from the **diff**, not from the commit messages. Commit messages say what each step did; the PR says what the branch changes and why anyone should care. ## Step 0 — Resolve the branch and its base Run `"${CLAUDE_PLUGIN_ROOT}"/scripts/branch-diff.sh $ARGUMENTS_BASE` (pass the base branch if `$ARGUMENTS` names one; otherwise let the script resolve it). It prints the base, merge base, commit list, per-file churn, name-status, and signal flags for dependency, schema, config and deletion changes. Stop and ask the user before going further if any of these hold: - **The branch is the base.** There is nothing to open a PR from. Say so and stop. - **Zero commits ahead.** Same. - **Uncommitted changes exist.** They will not be in the PR. Ask whether to proceed anyway or commit first, and stop until they answer. - **The resolved base looks wrong** (e.g. it resolved to `origin/master` in a repo that clearly uses `develop`). Name what it resolved to and ask. ## Step 1 — Read the diff Read the actual changes, not just the file list. For a large branch, read the files with the most churn plus every file flagged as a signal in Step 0. You are extracting four things: 1. **What changes for a user or a caller.** The observable difference. If there isn't one, say