prepare-paperclip-pr

Topics in the source

• Prepare Paperclip PR
• 0. Preconditions — worktree safety
• 1. Commit everything — lose no work
• 2. Get changes cleanly on top of master
• 3. Guardrails checklist (every PR)
• 4. Open the PR
• 5. Review loops
• 6. Report back and hand off

The standard Paperclip procedure for turning branch work into a reviewed, green pull request against paperclipai/paperclip master. Apply it once per PR (if a task splits a branch into several PRs, run the whole procedure for each one). Do all PR work in a git worktree on a dedicated branch. The main /paperclip checkout typically runs the live Paperclip server — never check out branches there. If you are already on a worktree/branch, verify it (git rev-parse --git-dir, git branch --show-current) and proceed. If the main checkout is unexpectedly off master, fix that first without losing work (usually: move that branch's work into a worktree). Confirm which remote/ref you are targeting (normally master on the paperclipai/paperclip repo; the task may name a specific remote such as origin or public-gh). Make logical commits of all uncommitted changes before anything else. Do not stash and forget; do not leave files behind. If commits are missing, make them. Commit messages must end with exactly: Co-Authored-By: Paperclip Fetch the target remote and rebase (or otherwise replay) your branch on top of the target master so the PR has no merge conflicts. Re-verify after rebase: build/tests r

This is an excerpt. Refer to the complete source and its current requirements.