source-control: remote name `origin` hardcoded in pull-request create flow (low severity)

[kyle-sexton]

Plugin: source-control · Category: baked repo assumption (1) — low severity
Source: work-readiness sweep (read-only audit vs docs/PLUGIN-PHILOSOPHY.md + docs/MIGRATION-PLAYBOOK.md)

Findings

• plugins/source-control/skills/pull-request/reference/create.md:71,159 — git fetch origin, git push -u origin <branch>

Why flagged

Real portability assumption: a consumer whose remote is not named origin (fork-based flows with upstream/fork, multi-remote setups) breaks. Common practice, so low severity — but the convention-resolution ladder's "no baked repo assumptions" applies.

Fix direction

Resolve the push remote (e.g. the current branch's configured remote, git config branch.<name>.remote, or gh repo set-default context) with origin as the documented fallback.

[kyle-sexton]

Lane

babysit (safe tier, /loop 15m /source-control:babysit-prs)

Triggering example

PR #467 (fix/411-default-branch-detection, toolchain plugin): worker fixed the identical hardcoded-origin class in plugins/toolchain/skills/check/SKILL.md and plugins/toolchain/skills/lint/SKILL.md (a codex P2 finding: git clone -o vendor breaks the default-branch-detection fallback since there's no origin). Fix resolved the remote via branch.<name>.remote with origin as fallback, mirroring plugins/repo-hygiene/skills/clean/scripts/git-tree-reset.sh's existing correct pattern.

While fixing that PR's two files, the worker flagged (but correctly left untouched, as out of that PR's branch scope) three more pre-existing hardcoded-origin copies in files this fix pass didn't touch:

• plugins/session-flow/skills/clean-stop/SKILL.md
• plugins/repo-hygiene/skills/*/scripts/git-branch-audit.sh (exact script path not re-verified by me, per worker's report)
• plugins/repo-fleet-hygiene/skills/*/scripts/audit-fleet.sh (exact script path not re-verified by me, per worker's report)

Observed vs expected

Same as this issue's existing framing — these are additional occurrences of the same "no baked repo assumptions" violation, just in different plugins than the originally-flagged pull-request/reference/create.md. Worth folding into this issue's fix-direction sweep (or splitting per-plugin follow-ups) rather than treating as isolated one-offs, since the fix pattern (branch.<name>.remote with origin fallback) is now demonstrated working in at least 2 places (git-tree-reset.sh, and now toolchain's check/lint).

Category

bug (same as existing)