fix: gh CLI 加 --repo 参数适配 workspace 本地 remote

[lishuceo]

Summary

• 工作区 git remote 指向本地缓存路径，gh CLI 无法自动识别 GitHub host
• 在普通模式 workspace prompt (executor.ts) 和 pipeline push prompt (prompts.ts) 中加入提示：始终使用 --repo owner/repo 参数
• PM bot 不受影响（走 systemPromptOverride 路径）

改动文件

• src/claude/executor.ts — buildWorkspaceSystemPrompt 新增 ## GitHub CLI (gh) 注意事项
• src/pipeline/prompts.ts — PUSH_SYSTEM_PROMPT 追加 gh 注意事项

[claude]

Claude finished @lishuceo's task in 1m 33s —— View job

---

PR Review: gh CLI --repo flag adaptation

• Check previous review comments
• Read changed files and understand context
• Review changes and post findings

Verdict: ✅ Approve with minor suggestions

Overall assessment: Clean, focused PR that solves a real problem — workspace git remotes point to local bare cache paths, so gh CLI can't auto-detect the GitHub repo. The fix correctly adds --repo owner/repo guidance to both the normal workspace prompt (executor.ts) and the pipeline push prompt (prompts.ts).

2 minor suggestions posted as inline comments:

• 🟡 prompts.ts:122 (confidence: 80) — Step 8 still shows gh pr create --fill without --repo, inconsistent with the new "all gh commands must use --repo" guidance right below it.
• 🟡 executor.ts:133 (confidence: 78) — Unlike prompts.ts which hints "从 git remote URL 或项目配置中推断 owner/repo", the executor prompt doesn't explain how the agent should determine the actual owner/repo value when the remote is a local path.

What looks good:

• Correct scoping — only affects workspace prompts, PM bot (systemPromptOverride path) is unaffected
• PR_FIXUP_SYSTEM_PROMPT doesn't need changes since it delegates to the /pr-fixup skill
• For writable mode workspaces cloned via repoUrl, the manager already resets origin to the real remote URL (manager.ts:165-168), so --repo is technically redundant there but doesn't hurt — safe/conservative guidance

---

[claude]

🟡 Minor inconsistency (confidence: 80)

Step 8 above (line 118) still shows gh pr create --fill without --repo, which contradicts the new guidance on lines 120-122 that says all gh commands must use --repo. An agent might follow the specific step 8 example and omit --repo.

Consider updating step 8 to be consistent:

Suggested change

	所有 \`gh\` 命令必须加 \`--repo owner/repo\` 参数（从 git remote URL 或项目配置中推断 owner/repo）。
	所有 \`gh\` 命令必须加 \`--repo owner/repo\` 参数（从 git remote URL 或项目配置中推断 owner/repo）。例如 \`gh pr create --fill --repo owner/repo\`。

[claude]

🟡 Missing guidance on how to resolve owner/repo (confidence: 78)

The examples use literal owner/repo as a placeholder, but unlike prompts.ts (which says "从 git remote URL 或项目配置中推断 owner/repo"), this prompt doesn't tell the agent how to determine the actual owner/repo value. Since the workspace remote points to a local cache path, git remote -v won't directly reveal the GitHub owner/repo.

Consider adding a hint, e.g.:

owner/repo 可以从项目 CLAUDE.md、git log 中的 GitHub 链接、或 bare cache 路径结构推断。