Bugfix workflow PR skill: hardcoded fork remote name contradicts Step 4 guidance

[jwm4]

Problem

In the PR skill (workflows/bugfix/.claude/skills/pr/SKILL.md), Step 4 says:

Use fork as the remote name. If origin already points to the fork, that's fine — just use origin in subsequent commands instead of fork.

But Step 7 hardcodes fork in the push command:

git push -u fork BRANCH_NAME

If the agent kept origin as the fork remote (per Step 4's guidance), this push command will fail.

Suggested fix

Add a FORK_REMOTE placeholder to the placeholders table, set it in Step 4 based on which remote points to the fork, and use it in all downstream commands (push, gh pr create --head, compare URL, git ls-remote).

Found by

CodeRabbit review on #79.