review-loop

Installation
SKILL.md

Review loop

Review a change with both models, verify what they report, fix it, and re-review until nothing actionable remains. The counterpart is the other vendor's model: Codex when Claude runs this skill, Claude Opus when Codex does. It catches the blind spots of the model that wrote the change. This skill coordinates: it verifies, merges, reports, and fixes, and adds no findings of its own.

/code-review owns the Standards and Spec rubric, /thermo-nuclear-review the correctness and security audit, /pstack-swarm dispatch and the counterpart route, and /pstack-principles selects the principles reviewers apply. Read the reviewer brief before dispatching a round.

Authority

Inside an implementation workflow, such as /implement, /implement-spec, or a Pstack playbook, the loop applies its fix findings and re-reviews without asking between rounds. A standalone review request reports round 1 and waits; the user's go then runs the whole loop. Public comments, merges, and PR state changes keep their own authorizations.

1. Pin the target

Resolve one target: a PR, branch, commit range, or file set the user names; a plan or spec; the current branch against its stack parent or its merge-base with the default branch; or the working changes. Read the intent from the spec and tickets, the PR description, or the accepted request. List the repository's standards documents, and invoke /pstack-principles in review mode for the applicable owners.

For a code target, build the packet from this skill's directory with node scripts/packet.ts --repo <repo>, adding --base <ref>, --since <ref>, --head <ref>, or --working as the target needs (--help explains each; Bun also runs it). The packet pins immutable revisions, snapshots working changes into a commit without touching the index or stash, and lists lockfiles, binaries, and generated or vendored files while leaving them out of the diff. A bad ref or an empty diff stops here.

Complete when: the target, intent, standards documents, selected principles, and either the packet's base and head or the plan's path are known.

2. Review

Installs
5
GitHub Stars
1
First Seen
2 days ago
Security Audits