ptp-review-loop

Drives iterative code and artifact review loops with severity thresholds and convergence markers.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-review-loop-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-review-loop
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-review-loop
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-review-loop-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes and planning artifacts often stalls in open-ended feedback cycles with no clear stopping point. This Skill runs a bounded review loop that confirms or rejects findings, applies fixes, and terminates at a defined convergence state or iteration cap. ## Core Features & Use Cases - Shared review loop protocol: Drives code, plan, brainstorm, and PRD review iterations for both in-session (ptp) and external Codex reviewers, with a configurable iteration cap (default 5). - Severity thresholding: Resolves a review.minSeverity floor (low/medium/high/critical) from layered config so low-priority findings are reported but do not block convergence. - Durable convergence markers: Writes per-kind stage records (stages/code.json, plan.json, etc.) with reviewer sets, tallies, and content fingerprints so later runs can skip redundant reviews. - Use Case: After implementing a change, run /ptp:review-loop to have findings reviewed, confirmed, fixed, and tallied until the diff converges or the iteration cap is reached, with a fingerprinted marker proving what was reviewed. ## Quick Start Ask the AI to run the ptp review loop on the current OpenSpec change so findings are reviewed, fixed, and converged within the iteration cap.

Frequently Asked Questions about ptp-review-loop

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

FAQPage Schema
How do I run an iterative code review loop in Claude Code?▼

Invoke /ptp:review-loop with a resolved OpenSpec change id. The loop reviews the diff, confirms or rejects each finding, fixes confirmed ones, and repeats until no in-scope findings remain or the iteration cap (default 5) is reached.

How do I set a minimum severity threshold for code review findings?▼

Set review.minSeverity in a ptp config.json layer to low, medium, high, or critical. Findings below that rank are reported but do not block convergence; invalid or missing values fall back to low without stopping the run.

Can I use Codex CLI as a second reviewer for code reviews?▼

Yes, the codex-review-loop variant dispatches review passes to the Codex CLI via codex exec while the loop semantics stay identical. The caller must verify codex is on PATH before invoking, and behavior when it is missing follows the codex.mode setting.

When can a code review be skipped based on a previous run?▼

A review can be skipped only when a converged stages/code.json marker exists with a recognized v2 fingerprint that recomputes to the same value, a sufficient reviewer set, and a minSeverity at least as strict as the current one. Any mismatch makes the marker ineligible and the review runs normally.

What happens when the review loop hits the iteration cap?▼

The loop terminates at ITERATION CAP REACHED, writes a cap-reached stage marker with the review tally, and reports open findings, rejected findings, and per-iteration summaries. A cap-reached marker never authorizes skipping a future review.