Agent skill · software engineering · aiskillstore
iterate-pr
Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.
Why this skill is useful
Adds an executable script that automates the CI feedback-fix-push cycle, significantly enhancing the agent's capability to manage pull requests.
What it needs
Requires gh installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Iterate on PR Until CI Passes Continuously iterate on the current branch until all CI checks pass and review feedback is addressed. When to Use This Skill Use this skill when: Fixing CI failures Addressing review feedback Continuously pushing fixes until all checks are green Automating the feedback-fix-push-wait cycle Ensuring PR meets all quality gates Requires: GitHub CLI (gh) authenticated and available. Process Step 1: Identify the PR If no PR exists for the current branch, stop and inform the user. Step 2: Check CI Status First 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. Step 3: Gather Review Feedback 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. Step 4: Investigate Failures For each CI failure, get the actual logs: Do NOT assume what failed based on the check name alone. Always read the actual logs. Step 5: Validate Feedback For each piece of feedback (CI failure or review comment): 1. Read the relevant code - Understand the context before making changes 2. Verify the issue is real - Not all feedback is correct; reviewers and bots can be wrong 3. Check if already addressed - The issue may have been fixed in a subsequent commit 4. Skip invalid feedback - If the concern is not legitimate, move on Step 6: Address Valid Issues Make minimal, targeted code changes. Only fix what is actually broken. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/iterate-pr--1f4237