Community코딩 & 개발github.com

getsentry/iterate-pr

PR의 CI가 통과하고 중요도가 높거나 중간인 리뷰 피드백이 반영될 때까지 반복적으로 개선합니다. PR CI 실패, 리뷰 피드백, 또는 green-check 루프에 사용하세요. 사람의 승인, 초안 상태, 또는 병합 게이트를 기다리지 않습니다.

iterate-pr란 무엇인가요?

이 스킬은 GitHub PR(풀 리퀘스트)이 CI(지속적 통합) 검사를 통과하고 중요도가 높거나 중간인 리뷰 피드백이 모두 해결될 때까지 자동으로 반복 개선하는 AI 에이전트 기능입니다. 개발자는 CI 실패나 리뷰 코멘트가 발생했을 때마다 수동으로 수정하고 다시 푸시하는 번거로움을 덜 수 있습니다. 이 스킬은 PR의 현재 상태를 분석하고, 필요한 코드 변경 사항을 식별하며, 변경 사항을 커밋하고 푸시하는 과정을 반복합니다. 사람의 승인이나 초안 상태 해제를 기다리지 않으므로, 개발자가 PR을 완전히 녹색 상태(green-check)로 만드는 데 집중할 수 있도록 돕습니다. GitHub Actions, CI/CD 파이프라인과 통합되어 작동하며, PR 설명이나 코멘트를 통해 활성화할 수 있습니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/getsentry/skills/tree/main/skills/iterate-pr

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

iterate-pr은(는) 무엇을 하나요?

PR의 CI가 통과하고 중요도가 높거나 중간인 리뷰 피드백이 반영될 때까지 반복적으로 개선합니다. PR CI 실패, 리뷰 피드백, 또는 green-check 루프에 사용하세요. 사람의 승인, 초안 상태, 또는 병합 게이트를 기다리지 않습니다.

작동 방식

  1. PR 분석: 현재 PR의 CI 상태와 리뷰 피드백을 분석합니다.
  2. 변경 사항 식별: CI 실패 또는 리뷰 피드백을 해결하는 데 필요한 코드 변경 사항을 식별합니다.
  3. 변경 및 푸시: 식별된 변경 사항을 적용하고 PR 브랜치에 푸시합니다.
  4. 반복: CI가 통과하고 중요 리뷰 피드백이 해결될 때까지 1-3단계를 반복합니다.

사용법

GitHub Actions 워크플로

name: Iterate PR
on:
  pull_request:
    types: [opened, synchronize, reopened]

jobs:
  iterate:
    runs-on: ubuntu-latest
    steps:
      - uses: getsentry/iterate-pr@v1
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}

환경 변수

변수설명필수
GITHUB_TOKENGitHub API 접근을 위한 토큰예
MAX_ITERATIONS최대 반복 횟수 (기본값: 5)아니요

주의사항

  • 이 스킬은 사람의 승인을 기다리지 않습니다.
  • PR이 초안(draft) 상태인 경우 작동하지 않습니다.
  • 병합 게이트(merge gates)가 설정된 PR은 건너뜁니다.
  • CI가 지속적으로 실패하는 경우 최대 반복 횟수 후 중단됩니다.

관련 리소스

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

getsentry/agents-md

Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.

getsentry/blog-writing-guide

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

getsentry/brand-guidelines

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

getsentry/claude-settings-audit

Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.

getsentry/code-simplifier

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

getsentry/commit

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

getsentry/create-branch

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

getsentry/django-access-review

Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python/Django code handling user authorization. Trigger keywords: "IDOR", "access control", "authorization", "Django permissions", "object permissions", "tenant isolation", "broken access".

getsentry/django-perf-review

Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.

getsentry/doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

getsentry/find-bugs

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

getsentry/gha-security-review

GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.

getsentry/gh-review-requests

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".

getsentry/presentation-creator

Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a deck", "create a data presentation", "build a Sentry presentation". Scaffolds a complete slide-based app with charts, animations, and single-file HTML output.

getsentry/pr-writer

Create, refresh, and rewrite PR titles and descriptions following Sentry conventions. Use when opening a PR, writing or updating a PR title/body/description, refreshing an existing PR after material changes, or preparing branch changes for review.

getsentry/security-review

Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.

getsentry/skill-scanner

Scan agent skills for security issues. Use when asked to "scan a skill", "audit a skill", "review skill security", "check skill for injection", "validate SKILL.md", or assess whether an agent skill is safe to install. Checks for prompt injection, malicious scripts, excessive permissions, secret exposure, and supply chain risks.

getsentry/skill-writer

Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation.

getsentry/sred-project-organizer

Take a list of projects and their related documentation, and organize them into the SRED format for submission.

getsentry/sred-work-summary

Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.

관련 스킬