ITSOL Code Review Workflow

Review the PR as a risk-control step: verify behavior, safety, tests, and maintainability before style preferences.

Extension-managed review policy

When the Pi extension exposes an effective review profile, treat it as the controlling contract:

• off: do not add review ceremony unless the user explicitly requests a review.
• poc: perform at most one lightweight final inline review; do not delegate or automatically re-review.
• balanced: let the main agent decide whether formal review is worth its cost, then use one proportionate inline or specialist pass; do not automatically re-review by default.
• strict: require risk-based independent coverage and re-review after actual fixes until approved or the configured cap is reached.

trigger=manual means review runs only on explicit request; trigger=adaptive delegates the run/skip and depth decision to the main agent; trigger=final means once before completion, not after each edit. delegation=never authorizes inline review even for surfaces that would normally require specialists. Automatic re-review requires a prior material changes-requested verdict, a changed diff fingerprint, and an available round. Never silently exceed max_rounds or execution.max_review_rounds.

Process