docs: add Run PR shortcut for automated open-PR maintenance sweeps#980
Merged
Conversation
Typing "Run PR" as the task message now triggers a one-shot sweep over every open PR: fix failing required CI checks, address and resolve review threads, and merge origin/main into drifted branches, then push. - AGENTS.md: new "Run PR shortcut" policy section (trigger, scoped authorization carve-out from the API/provider confirmation boundary, hard guardrails: never merge/auto-merge/close/force-push/rebase, never provider-backed gates, skip-codex-review opt-out), plus cross-references in the confirmation-boundary and pr-ci-fix routing. - .claude/skills/run-pr/SKILL.md: canonical procedure — sweep setup, per-PR algorithm (skip gates, drift-first merge with conflict rules, CI diagnosis with job-to-local-command map, thread fix/reply/resolve mechanics, iteration caps), ledger row format, and report format. - .claude/agents/pr-ci-fixer.md: note that an explicit Run PR sweep already carries the user's authorization so the subagent does not stall the sweep on a confirmation request. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vc5z2HPfZSAbeg43Pu9CpY
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds a ChangesRun PR sweep
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant User
participant RunPR
participant GitHub
participant Worktree
participant Ledger
User->>RunPR: Type Run PR
RunPR->>GitHub: Enumerate and snapshot open PRs
RunPR->>Worktree: Diagnose and verify permitted fixes
Worktree->>GitHub: Push allowed changes
RunPR->>GitHub: Reply to and resolve eligible threads
RunPR->>Ledger: Record per-PR results
RunPR-->>User: Return consolidated report
Possibly related PRs
Suggested labels: ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
BigSimmo
marked this pull request as ready for review
July 20, 2026 09:36
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
BigSimmo
enabled auto-merge (squash)
July 20, 2026 09:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Run PRchat shortcut: when the user types exactlyRun PRas the task message, the assistant runs a one-shot maintenance sweep over every open PR (drafts included) — fixing failing required CI checks, addressing unresolved review threads (fix, reply, resolve), and mergingorigin/maininto behind/conflicting branches before pushing.AGENTS.md: new## Run PR shortcutpolicy section (trigger recognition, a scoped authorization carve-out from the "API and provider confirmation boundary", and hard guardrails — never merge/auto-merge/close/force-push/rebase, never provider-backed gates,skip-codex-reviewlabel as a full opt-out), plus one-line cross-references in the confirmation-boundary block and thepr-ci-fixrouting bullet..claude/skills/run-pr/SKILL.md(new): the canonical procedure — sweep setup, per-PR algorithm (skip gates, drift-firstgit merge origin/mainwith conflict rules, CI diagnosis with a job→local-command reproduction map, thread fix/reply/resolve mechanics, per-PR iteration caps), branch-review-ledger row format, and the final report format..claude/agents/pr-ci-fixer.md: notes that an explicitRun PRsweep already carries the user's authorization, so the diagnose-only subagent doesn't stall the sweep asking for a confirmation the user has already given.Verification
Docs/skill-only change — no product, config, or test code touched, so the standard gates don't apply. Verification run:
npm run check:skills— passes; the validated.agents/skills/catalog is untouched (still 32 canonical skills, 8 aliases).npx prettier --check AGENTS.md .claude/skills/run-pr/SKILL.md .claude/agents/pr-ci-fixer.md— passes (these paths are covered by CI's format gate).## Run PR shortcutheading and oneBEGIN:run-pr-shortcut/END:run-pr-shortcutdelimiter pair inAGENTS.md.Verification not run:
verify:pr-local/verify:ui/verify:release— no runtime surface changed; the diff is agent-instruction Markdown only.Risk and rollout
Run PRbecomes standing authorization for a scoped set of GitHub actions (pushes to PR feature branches, thread replies/resolution, CI re-runs, branch updates from main). The guardrail list explicitly keeps merging, auto-merge, closing PRs, force-pushes, branch deletion, and provider-backed gates confirmation-required.Clinical Governance Preflight
Not applicable — no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output touched.
Notes
<!-- codex-thread-disposition:resolved -->marker (the autofix workflow only trusts it from the Codex bot); threads are resolved directly via the GitHub MCP tool after a reply.Generated by Claude Code
Summary by CodeRabbit
New Features
Documentation