closing-review-loops

Batches code review fixes into one verified push before re-triggering external reviewers.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill closing-review-loops-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: closing-review-loops
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/closing-review-loops
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill closing-review-loops-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-authored pull requests churn through repeated review rounds when fixes are pushed comment-by-comment, each push re-triggering external reviewers and CI. This Skill closes each review round in a single batched, self-reviewed push so the PR converges in as few external rounds as possible. ## Core Features & Use Cases - Batched fix pass: Collects every open finding across all threads and reviewers, fixes them in one pass using verify-then-fix discipline, and pushes exactly once. - Adversarial internal self-review: Dispatches internal reviewers against the current diff to hunt the same failure classes already found in the PR plus regressions introduced by the fixes themselves. - Round-level measurement: Re-checks branch cohesion and reports cumulative commits and LOC delta versus base every round, catching PRs that quietly grow past size gates across sessions. - Use Case: A reviewer leaves 8 comments on an open PR. Instead of 8 push-and-reply cycles, you batch all findings, fix and verify them, run an internal adversarial review until clean, push once, and only then re-trigger the external bot. ## Quick Start After addressing review feedback on my pull request, run the closing-review-loops process to batch the fixes, self-review the diff, and push once before re-triggering the external reviewer.

Frequently Asked Questions about closing-review-loops

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

FAQPage Schema
How do I handle multiple code review comments on a pull request?

Batch every open finding across all threads into one fix pass, verify each fix, run an internal self-review on the current diff, then push once. Avoid pushing per comment, since each push re-triggers external reviewers and CI.

How to reduce review rounds on AI-generated pull requests?

Run an internal adversarial self-review before re-triggering the external reviewer, instructing it to hunt the same failure classes already found plus regressions the fixes introduced. Only push when that internal pass comes back clean.

When is it acceptable to skip the internal self-review before re-review?

Only for a genuine emergency, and only with an explicit override reason recorded in the PR thread, such as a hotfix for an active SEV-1 incident. Without that recorded reason, the internal-review gate is binding.

Does this apply to PRs already in review or only new submissions?

It binds to PRs already in review. When a reviewer leaves N comments on an open PR, batch all N, fix in one pass, self-review, push once, and reply to threads only after the verified push.

Why does my pull request keep growing across review rounds?

Branches drift through many individually small, justified rounds. The skill's measurement step re-checks cohesion and reports cumulative commits and LOC delta versus base every round, surfacing growth before it forces a split.