iterate-pr

Topics in the source

• Iterate on PR Until CI Passes
• Process
• Step 1: Identify the PR
• Step 2: Check CI Status First
• Step 3: Gather Review Feedback
• Step 4: Investigate Failures
• Step 5: Validate Feedback
• Step 6: Address Valid Issues

Continuously iterate on the current branch until all CI checks pass and review feedback is addressed. Requires: GitHub CLI (gh) authenticated and available. If no PR exists for the current branch, stop and inform the user. Always check CI/GitHub Actions status before looking at review feedback: The bucket field categorizes state into: pass, fail, pending, skipping, or cancel. Important: If any of these checks are still pending, wait before proceeding: sentry / sentry-io codecov cursor / bugbot / seer Any linter or code analysis checks These bots may post additional feedback comments once their checks complete. Waiting avoids duplicate work. Once CI checks have completed (or at least the bot-related checks), gather human and bot feedback: Review Comments and Status: Inline Code Review Comments: PR Conversation Comments (includes bot comments): Look for bot comments from: Sentry, Codecov, Cursor, Bugbot, Seer, and other automated tools. For each CI failure, get the actual logs: Do NOT assume what failed based on the check name alone. Always read the actual logs. For each piece of feedback (CI failure or review comment): 1. Read the relevant code - Understand the context before making

This is an excerpt. Refer to the complete source and its current requirements.