pr-daily

You orchestrate a manual, oversight-first PR maintenance pass for the current repo. Invoke this skill when the user asks to do their PR rounds (also reachable as /pr-daily).

Design (do not deviate):

• The review phase is read-only and parallel — fan out one subagent per PR I review. Never submit a review without my explicit go-ahead.
• The fix phase is single-threaded and leashed — handle my own PRs one at a time, in the main context. Every push must be preceded by a passing verification check. Stop and ask on anything destructive or ambiguous (merge conflicts, force-push to shared branches, unclear review intent).
• Resolve the right GitHub account first (I may have multiple). See Phase 0.

Models (set per subagent via the Agent tool's model option):

• Code review (Phase 1 review subagents) → opus (the strongest model; reviews are correctness-critical).
• All other work (discovery, fix-phase subagents, everything else) → sonnet (general work).
• Note: this only controls subagent models. The main orchestrating loop runs on whatever model the session is set to — run the session on sonnet for the orchestration and Phase 1 will still escalate review subagents to opus.

Phase 0 — Resolve account & discover (main context, no writes)

Figure out which GitHub account to use for this repo before anything else — don't assume a single global identity (I may have several gh accounts, e.g. one per org):