Generated banner for Iterate Pr
Generated logo for Iterate Pr

Iterate Pr

SentryOfficialPublished by Sentry

  • Skill
  • Workflow
  • Software development
  • Apache-2.0
  • Low risk
  • Has scripts

From the author

Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.
— the description by Sentry

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The iterate-pr skill provides a structured workflow for managing pull requests by automatically monitoring CI status and review feedback. It guides an agent to identify actionable failures, apply fixes, and verify changes locally before pushing updates. The process focuses on resolving high and medium priority issues while intelligently handling low-priority feedback and ignoring non-actionable gates like human approvals or draft status.

What it does

  • Fetches and categorizes PR feedback into high, medium, and low priority buckets.
  • Monitors CI check status to distinguish between actionable failures and pending gates.
  • Provides a systematic loop for fixing root causes of CI failures and pushing updates.
  • Handles low-priority feedback by prompting the user for guidance.
  • Uses specialized scripts to interact with PR metadata, checks, and review threads.
  • Includes fallback procedures using standard CLI tools if automated scripts encounter errors.

When to use it

  • When a PR has failed CI checks that require code adjustments.
  • When there is high or medium priority review feedback that needs to be addressed.
  • To automate the repetitive cycle of fixing, testing, and pushing code to a PR.
  • When you need to ensure a PR is clean and ready for human review without manual intervention.

Advantages

  • Reduces manual overhead in the PR feedback and CI repair loop.
  • Ensures consistent handling of feedback priorities.
  • Focuses on root cause resolution rather than symptomatic fixes.
  • Integrates seamlessly with existing CI/CD workflows and GitHub CLI.

Usage examples

“Iterate on PR #123 until all CI checks pass.”
The agent will fetch the PR status, identify failed checks, apply necessary fixes, and continue looping until all actionable CI failures are resolved.
“Address the high and medium feedback on my current PR.”
The agent will retrieve the review comments, categorize them, and systematically apply fixes for all high and medium priority items.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/getsentry/iterate-pr/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip iterate-pr.zip -d .agents/skills

Documentation by Sentry

Iterate on PR Until CI Passes

Goal: fix actionable CI failures and high/medium review feedback. Stop and report human approval, draft-readiness, and merge-readiness gates.

Requires:

  • authenticated gh

  • uv

  • target repository root as cwd

  • skill-root-relative script paths, for example scripts/fetch_pr_checks.py

Bundled Scripts

ScriptRunOutput
scripts/fetch_pr_checks.pyuv run scripts/fetch_pr_checks.py [--pr NUMBER]JSON: pr, summary, checks, failure snippets
scripts/fetch_pr_feedback.pyuv run scripts/fetch_pr_feedback.py [--pr NUMBER]JSON buckets: high, medium, low, bot, resolved
scripts/monitor_pr_checks.pyuv run scripts/monitor_pr_checks.py [--pr NUMBER]terminal marker plus tab-separated checks
scripts/reply_to_thread.pyuv run scripts/reply_to_thread.py THREAD_ID BODY [...]JSON reply results

Check summary fields include failed, pending, actionable_pending, and human_gate_pending.

Monitor markers:

  • ALL_CHECKS_PASSED

  • CHECKS_DONE_WITH_FAILURES

  • NO_CHECKS_REGISTERED

  • DRAFT_PR_WITH_NO_CHECKS

  • CHECKS_BLOCKED_BY_REVIEW_GATE

Workflow

1. Identify PR

Run:

gh pr view --json number,url,headRefName,isDraft,reviewDecision

Stop when:

  • no PR exists

  • draft PR has no checks after monitor grace period: report DRAFT_PR_WITH_NO_CHECKS

Draft rule: inspect existing checks/feedback only. Do not mark ready for review unless asked.

2. Handle Feedback

Run uv run scripts/fetch_pr_feedback.py [--pr NUMBER].

BucketAction
highfix
mediumfix
lowask user which to address
botskip informational comments
resolvedskip

Feedback fix checklist:

  • verify root cause

  • search related code

  • fix all instances

  • for review_bot: true: fix real issues, explain false positives

Low-priority prompt format:

Found 3 low-priority suggestions:
1. [l] "Consider renaming this variable" - @reviewer in api.py:42
2. [nit] "Could use a list comprehension" - @reviewer in utils.py:18
3. [style] "Add a docstring" - @reviewer in models.py:55

Which should I address? ("1,3", "all", or "none")
3. Check CI Status

Run uv run scripts/fetch_pr_checks.py [--pr NUMBER].

StateAction
failed > 0 and actionable_pending == 0fix failures
actionable_pending > 0wait; poll feedback while waiting
pending > 0 and actionable_pending == 0report CHECKS_BLOCKED_BY_REVIEW_GATE
no checks after grace periodreport NO_CHECKS_REGISTERED or DRAFT_PR_WITH_NO_CHECKS
all actionable checks passedrun post-CI feedback check

Wait for actionable review bots: sentry, warden, cursor, bugbot, seer, codeql. Do not wait for approval, isDraft, REVIEW_REQUIRED, Codecov, or informational bots.

4. Fix CI Failures

For each failure:

  1. read full log: gh run view <run-id> --log-failed

  2. trace from assertion/exception/lint rule to source

  3. state the cause before editing: "fails because X, affected by Y"

  4. search related call sites/patterns

  5. fix root cause, not symptom

  6. add focused test coverage when needed

5. Verify Locally, Then Commit and Push

Before commit:

  • test fix: rerun specific test

  • lint/type fix: rerun affected checker

  • code fix: rerun covering tests

  • local failure: fix before pushing

git add <files>
git commit -m "fix: <descriptive message>"
git push
6. Monitor CI and Address Feedback

Loop:

  1. run uv run scripts/fetch_pr_checks.py

  2. handle table in step 3

  3. while actionable_pending > 0, run uv run scripts/fetch_pr_feedback.py

  4. fix new high/medium feedback immediately

  5. if changed, verify, commit, push, restart loop

  6. otherwise sleep 30 seconds and repeat

  7. after checks pass, wait 10 seconds, fetch feedback once more

  8. if new high/medium feedback exists, return to step 4

Claude Code optional: run uv run scripts/monitor_pr_checks.py through MonitorTool with persistent: false; set timeout to normal repo CI duration. Restart the monitor after every push.

Exit Conditions

ExitConditions
Successactionable CI passed; post-CI feedback clean; low-priority choice handled
Ask usersame failure after 2 attempts; feedback unclear; infrastructure issue
Stopno PR; branch needs rebase; no checks; draft no-checks; only human gates remain

Fallback

If scripts fail, use gh CLI directly:

  • gh pr view --json number,url,headRefName,isDraft,reviewDecision

  • gh pr checks --json name,state,bucket,description,link

  • gh run view <run-id> --log-failed

  • gh api repos/{owner}/{repo}/pulls/{number}/comments

Files

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter, Needs a command-line tool, Needs Python

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Sentry
Publisher
Sentry (Official)
Source
getsentry/skills · skills/iterate-pr · commit e94f222
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Sentry or Sentry.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download iterate-pr.zip