์Šคํ‚ฌ iterate-pr
๐Ÿ”„

iterate-pr

๋‚ฎ์€ ์œ„ํ—˜ โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด๐Ÿ“ ํŒŒ์ผ ์‹œ์Šคํ…œ ์•ก์„ธ์Šค

Iterate on pull requests until CI passes

๋˜ํ•œ ๋‹ค์Œ์—์„œ ์‚ฌ์šฉํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค: sickn33,getsentry

Managing CI failures and review feedback requires repeatedly checking status, applying fixes, and pushing changes. This skill automates the feedback-fix-push cycle so developers can focus on writing code instead of manually tracking CI pipelines.

์ง€์›: Claude Code(CC)
โš ๏ธ 66 ๋‚˜์จ
1

์Šคํ‚ฌ ZIP ๋‹ค์šด๋กœ๋“œ

2

Claude์—์„œ ์—…๋กœ๋“œ

์„ค์ • โ†’ ๊ธฐ๋Šฅ โ†’ ์Šคํ‚ฌ โ†’ ์Šคํ‚ฌ ์—…๋กœ๋“œ๋กœ ์ด๋™

3

ํ† ๊ธ€์„ ์ผœ๊ณ  ์‚ฌ์šฉ ์‹œ์ž‘

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"iterate-pr" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. My PR has 2 failing tests and a review comment. Fix them.

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Found PR #123 for branch feature/login
  • CI Status: 2 failed (test-unit, test-integration)
  • Found 1 review comment from @reviewer
  • Analyzing test failures...
  • Addressing review comment...
  • Changes committed and pushed
  • Watching CI... (checks passing: 5/7)
  • Waiting for remaining checks...
  • All CI checks passed! PR ready for merge

๋ณด์•ˆ ๊ฐ์‚ฌ

๋‚ฎ์€ ์œ„ํ—˜
v5 โ€ข 1/17/2026

Documentation-only skill providing CI/CD workflow guidance. Uses standard GitHub CLI commands for PR iteration. All commands match the stated purpose of PR automation. Static findings are false positives - backticks flagged as shell execution are actually markdown code block markers in documentation.

2
์Šค์บ”๋œ ํŒŒ์ผ
374
๋ถ„์„๋œ ์ค„ ์ˆ˜
3
๋ฐœ๊ฒฌ ์‚ฌํ•ญ
5
์ด ๊ฐ์‚ฌ ์ˆ˜
๋‚ฎ์€ ์œ„ํ—˜ ๋ฌธ์ œ (1)
SKILL.md:91-93
Git command execution with staged changes
The skill includes git commands that stage and commit changes: `git add -A`, `git commit -m`, and `git push`. These commands modify the local repository and push changes to remote. An attacker with control over the skill execution could manipulate commit messages or push unintended changes.

์œ„ํ—˜ ์š”์ธ

โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด (4)
SKILL.md:16-18 SKILL.md:26-28 SKILL.md:45-57 SKILL.md:65-71
๐Ÿ“ ํŒŒ์ผ ์‹œ์Šคํ…œ ์•ก์„ธ์Šค (1)
SKILL.md:91-93
๊ฐ์‚ฌ์ž: claude ๊ฐ์‚ฌ ์ด๋ ฅ ๋ณด๊ธฐ โ†’

ํ’ˆ์งˆ ์ ์ˆ˜

38
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
81
์ฝ˜ํ…์ธ 
19
์ปค๋ฎค๋‹ˆํ‹ฐ
88
๋ณด์•ˆ
91
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Fix CI failures automatically

Continuously fix test failures and linting issues until all CI checks pass without manual polling

Address review feedback efficiently

Track and resolve human review comments across multiple iteration cycles until approval

Monitor bot feedback

Wait for Sentry, Codecov, and other bot checks to complete before addressing their feedback

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Basic PR iteration 
Use the iterate-pr skill to fix the failing CI checks on my current PR
Address review feedback 
Check my PR for review feedback and address all comments using iterate-pr
Full CI verification 
Run iterate-pr to ensure all CI checks pass and all feedback is addressed before merge
Debug persistent failures 
Use iterate-pr to investigate why my CI is failing repeatedly and determine if it needs user intervention

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Verify the PR exists for your current branch before starting the iteration
  • Wait for bot-related checks (Sentry, Codecov) to complete before addressing their feedback
  • Validate that feedback is legitimate and not already addressed before making changes
  • Let the skill stop and ask for help when failures persist beyond 3 attempts

ํ”ผํ•˜๊ธฐ

  • Running the skill without GitHub CLI authentication or proper repository permissions
  • Ignoring pending CI checks and addressing feedback too early
  • Assuming all feedback is correct without validating the issue first
  • Continuing iteration when CI failures are infrastructure issues unrelated to your code

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

Does this skill work with GitHub Enterprise?
Yes. The GitHub CLI (gh) works with GitHub Enterprise Server installations when properly authenticated.
How long does it wait between CI checks?
By default, it polls every 30 seconds using `gh pr checks --watch --interval 30` for efficient monitoring.
Can I customize which CI checks to wait for?
Yes. Use `gh pr checks --required` to focus only on required checks and skip optional ones.
Is my data safe when using this skill?
Yes. The skill only reads PR metadata and pushes commits you explicitly approve. No data is sent to external servers.
What happens if CI keeps failing?
The skill stops after 3 failed attempts and asks for your help. This catches flaky tests or deeper issues requiring investigation.
How is this different from GitHub Actions auto-merge?
This skill actively investigates failures, applies code fixes, and addresses review feedback. Auto-merge only combines passing checks.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

davila7

๋ผ์ด์„ ์Šค

MIT

๋ฆฌํฌ์ง€ํ† ๋ฆฌ

https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/sentry/iterate-pr

์ฐธ์กฐ

main

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md