keel-review-cycle

Automate GitHub pull request review and fix cycles with multiple reviewers.

4|Updated May 23, 2026
One-click install
npx skills add https://github.com/berkayturanci/keel --skill keel-review-cycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keel-review-cycle
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-review-cycle
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-review-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The keel-review-cycle Skill unit helps streamline the review and fix cycles for pull requests (PRs) by facilitating parallel reviews, structured findings, and capped fix rounds.

Core Features & Use Cases

  • Parallel Reviews: Concurrently review the same PR diff with multiple reviewers.
  • Structured Findings: Post findings with clear severity levels and suggested fixes.
  • Capped Fix Rounds: Limit the number of fix rounds to avoid endless iterations.
  • Use Case: Imagine you have a PR with complex changes that requires thorough review. Use this Skill to ensure a structured review process with clear expectations for fixes and progress.

Quick Start

Run the keel command review-cycle with the PR numbers you want to review, e.g., keel review-cycle 12345 67890.

Frequently Asked Questions about keel-review-cycle

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

FAQPage Schema
How do I automate GitHub pull request reviews with multiple parallel reviewers?▼

Automate GitHub pull request reviews by running the keel CLI review-cycle command with specific PR numbers to concurrently coordinate multiple reviewers and consolidate structured feedback.

What is the best way to structure PR review findings and limit fix rounds?▼

Structure PR review findings by posting feedback with clear severity levels and suggested fixes, while configuring capped fix rounds to prevent endless iteration cycles on complex changes.

Do I need GitHub API access to run the review cycle for pull requests?▼

Yes, GitHub API access is required to automate the review cycle, as the Skill depends on the github-api to handle PR state, coordinate reviewers, and consolidate feedback.

How do I start a review cycle for a specific pull request?▼

Start a review cycle by executing the keel command `review-cycle` followed by the target PR numbers, such as `keel review-cycle 12345 67890`, to initiate parallel reviews.

Can I review multiple pull requests concurrently using this review cycle approach?▼

Yes, you can review multiple pull requests concurrently by passing several PR numbers to the keel review-cycle command, facilitating parallel reviews and structured findings across them.