fork-and-prlisted

# Fork and PR Walk a contributor through the standard "fork + branch + commit + push + PR" flow against a GitHub repo they don't have write access to. The user knows what they want to change; this skill codifies the boring `gh`/`git` syntax around it so they don't have to remember it. ## When this applies Trigger when the user wants to contribute upward to a repo they don't own. Common phrasings: "I want to make a PR to X", "contribute a fix to X", "fork and PR", "open a PR against the upstream X repo", or right after a `git push` fails with 403 on a clone of someone else's repo. Skip when: - The user owns the repo (just `git push` + `gh pr create` – no fork needed). - The user is hitting a SAML SSO 403 on `gh` itself (`Resource protected by organization SAML enforcement`). That's a one-time per-org token authorization at `https://github.com/settings/tokens`, not a per-PR step. Tell them to grant SSO on their `gh` CLI token and retry; don't try to drive that through this skill. - The contribution is a stacked-diff or multi-PR series (this skill assumes one branch → one PR). ## Inputs from the user Usually one or more of: - **Upstream repo** (`owner/name` or full URL, e.g. `SalesforceCommerceCloud/plugin_sitemap`). - **What they want to change** (a one-line intent, used to suggest a branch name). - **Where they're starting from** – fresh, or already inside a clone. If the upstream repo isn't named, ask. If the intent isn't named, ask before step 3 (branch naming) – no