Manage PRs

Use gh for fetching PR metadata, diffs, and CI status. Use local git for checkout, rebase, conflict resolution, and merge — it is more reliable for hands-on work.

Default merge: --squash --delete-branch. Stop and ask only on: auth errors (401/403), network timeouts, or irreversible cross-subsystem decisions.

Principles

• Read every diff before acting. CI green is not sufficient — gh pr diff <n> and verify logic.
• Decide autonomously. You have the diff — decide and document why. Don't ask the user about content decisions.
• Comment, don't close. When a PR needs work, leave a specific actionable comment explaining what to fix — don't close it. The author (human or agent) can iterate in the existing PR. Only close PRs that are truly abandoned, superseded, or duplicate.
• Resolve conflicts locally when the PR has value. Investigate the diff. If worthwhile, checkout, rebase, resolve, force-push.
• Verify at every gate. Run lint, tests, and/or build checks after conflict resolution, after any local changes, and before merging. Don't merge without a green local verification.
• Prefer local git over gh for branch manipulation. gh pr merge for clean merges. For anything involving branches, rebases, or conflicts — use git directly.

DO NOT