Automated-Code-Review-Cycle

Automate GitHub PR review cycles with Codex and Gemini feedback.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill automated-code-review-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Automated-Code-Review-Cycle
Source: https://github.com/SAZO-KR/sazo-toolkit/tree/main/packages/ai-harness/skills/automated-code-review-cycle
Command: npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill automated-code-review-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

자동으로 Codex와 Gemini의 PR 코드 리뷰를 수집하고, 피드백을 적용한 뒤 재리뷰를 사용자 개입 없이 반복합니다. Gemini가 비활성화된 저장소에서도 Codex만으로 판단합니다.

Core Features & Use Cases

  • End-to-end PR review automation: Codex와 Gemini에서 피드백을 수집하고 재리뷰를 반복하는 전체 워크플로를 자동화합니다.
  • Quota-aware retry & fallbacks: 리뷰 피드백 부족이나 쿼타 초과 상황에서 자동으로 대체 경로를 시도합니다.
  • 자동 커밋/푸시/답변 생성: 수정사항을 커밋하고 푸시한 후 리뷰에 답변으로 커밳 링크를 제공합니다.

Quick Start

PR를 생성하면 이 스킬이 Codex/Gemini의 리뷰를 자동으로 수집하고 수정사항을 반영한 뒤 커밋하고 푸시하여 재리뷰를 반복합니다.

Frequently Asked Questions about Automated-Code-Review-Cycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull request code reviews with Codex and Gemini?

Automated PR code reviews collect feedback from Codex and Gemini, apply fixes, commit, push, and re-submit until all reviewers pass without manual intervention. The workflow detects the target PR, fetches feedback, evaluates it, and posts structured replies automatically.

Can I run automated code review cycles using only Codex if Gemini is disabled?

Yes, automated code review cycles work with Codex alone in repositories where Gemini is disabled. The workflow safely falls back to Codex-only evaluation, handling quota checks and feedback collection independently without requiring Gemini integration.

What happens when Codex or Gemini hits a quota limit during a PR review cycle?

When a quota limit is hit during a PR review cycle, the workflow triggers safe fallback paths and retry logic. It evaluates available feedback, attempts alternative routes, and pauses re-submission to prevent failures from exceeding API limits.

How does an automated bot apply fixes to a pull request after receiving code review feedback?

After receiving code review feedback, the bot evaluates the comments, applies fixes locally, runs tests, commits the changes, and pushes them to the pull request branch. It then posts a structured reply with the commit link for reviewer visibility.

What is the best way to handle repetitive pull request review cycles without manual intervention?

The best way to handle repetitive PR review cycles is end-to-end automation that records cycle start time, fetches feedback, applies fixes, runs tests, commits, pushes, and re-submits until all reviewers pass, with built-in quota-aware retries and safe fallbacks.