Skip to main content

Automated Review Workflows

Three complementary layers can feed the same review process:

  • Deterministic checks: templates/workflows/pr-review.yml invokes executable scripts/ci-gate.sh and fails when absent. The adopter supplies commands, dependencies and selection. Server policy must require the actual reported check for it to block merging.
  • Optional AI bot review: the supplied ai-review job is credential-gated and advisory. Skipped, unavailable or failed review is not a clean completed review. Authorize source processing before configuring an external reviewer.
  • Specialist review: use §7.3’s effect table and project-specific templates; record scope and completion.

Use targeted local checks during iteration and comprehensive adopted CI checks for the exact candidate. Retain an installed local gate until its cadence is changed through the project’s control process. Full local duplication is not a universal requirement.

All layers feed s4u-code-review: preserve discrepancies against approved intent, investigate defects, record evidence status and resolve findings. A source file, template, check name or quiet bot does not prove execution or enforcement. Offline fixtures establish the entry point’s behaviour; adoption needs an installed-control probe.