Code Review Cycle

This skill appears to do what it says: orchestrate a coder (A) and reviewer (B) loop. Before installing or running it, consider: 1) The reviewer role is only a behavioral constraint in the instructions — the platform or model must enforce 'read-only'; it is not technically enforced by the script. 2) A's output (diffs, code) is passed into B as plain text — do not use this on sensitive/private code or secrets unless you trust the models/providers. 3) The helper script is small and only prints JSON payloads; still review the script locally before running. 4) If you need stronger guarantees (e.g., enforce reviewer cannot write files, avoid exposing whole files), add procedural checks or policy controls in your environment. If any of these concerns are unacceptable, avoid using the skill or run it only on non-sensitive repositories.