review

Automate multi-round GitHub pull request reviews with inline comments.

4|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/supersuit-tech/permission-slip --skill review-supersuit-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/supersuit-tech/permission-slip/tree/main/.claude/skills/review
Command: npx skills add https://github.com/supersuit-tech/permission-slip --skill review-supersuit-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing large pull requests across multiple rounds is time-consuming and error-prone. This skill streamlines the process by performing up to six rounds of review with structured inline comments, prioritizing findings by severity, and waiting between rounds to allow for fixes.

Core Features & Use Cases

  • Multi-round reviews: Conduct up to 6 rounds of code review, each generating inline comments on security, architecture, maintainability, and quality.
  • Timed pacing: Waits 5 minutes between rounds to give developers time to address issues and re-evaluate diffs.
  • No-commit policy: Review is strictly read-only, never modifying code or making changes.
  • Use this for PRs that require deep architectural critique, security review, or maintainability assessments before merge.

Quick Start

Provide a comprehensive PR review using up to six rounds, pausing between rounds to verify fixes and posting inline comments for found issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate multi-round PR code reviews on GitHub?

Automating multi-round PR code reviews involves running up to six review cycles that fetch new diffs and post inline GitHub comments by severity. The process pauses for five minutes between rounds to allow developers time to implement fixes before re-evaluating the changes.

What is the best way to add inline comments to GitHub pull requests by severity?

Adding inline comments to GitHub pull requests by severity is best handled by an automated review process that evaluates security, architecture, and maintainability. This approach uses the GitHub API to issue COMMENT reviews, categorizing findings by priority and avoiding duplicate comments across rounds.

Can I perform a read-only GitHub PR review without modifying code?

Performing a read-only GitHub PR review without modifying code is possible using an automated reviewer persona that enforces a strict no-commit policy. This ensures the review process only posts inline comments and tracks activity without ever pushing changes to the repository.

How does an automated code review track fixes between rounds?

Automated code reviews track fixes between rounds by pausing for a set interval, typically five minutes, after posting comments. The system then fetches new diffs to verify if developers have addressed the issues, tracks the current round number, and continues evaluating up to six rounds.

When do I need an automated multi-round code review for my pull requests?

An automated multi-round code review is needed for pull requests requiring deep architectural critique, security review, or maintainability assessments before merge. It is especially useful for large PRs where manual reviews across multiple iterations are time-consuming and error-prone.