Teaches an agent how to contribute to a repo it cannot push to: fork, keep the two remote layouts straight, file the pull from the fork, deal with CI approval, resubmit, and clean up after the merge. The --clone layout is the trap: origin becomes the fork, so a bare pr create files against your own copy and exits 0, and the working spelling --remote upstream --fork origin appears in no help or hint.
It earns a topic because the fork requirement surfaces only when pr create is refused, a fork's CI cannot be approved by its author, and --fork must be repeated on every resubmit even though the pull records its source.
🤖 Generated with Claude Code