Skip to main content
Installing enforcement without knowing what it will block is how a gate ends up being switched off a day later. Gate Preview scans your project and shows how it scores against all five presets at once, before anything is enabled. It is read-only: no config is written and no push is blocked until you choose to act on it.

Opening it

Scroll to the bottom of the File tab in the sidebar and click Preview Gate. Iris Code runs a background workspace scan and renders the results inline, respecting your ignoreFiles list.

The five presets

Ordered from most lenient to most strict:

What the preview shows

  • Workspace average - a single score across every file scanned
  • Files analysed - how many were included
  • Threshold card - which presets you already pass, and the next one you would fail
  • Recommendation - the strictest preset you could adopt today with nothing blocked
  • Focus card - one preset in detail, with controls to step through the others and an Apply button
  • Preset grid - all five at a glance, each clickable
The focus card shows the preset, its minimum score, how many files fail, and on Pro, which ones. Apply writes presetId into .irisconfig.json directly, without opening the file.

Free and Pro

The preview is free for everyone. Seeing the individual failing files, and enforcing the result, require Pro.

Acting on the results

On Free, add "presetId": "balanced" (or whichever preset you chose) to .irisconfig.json. The whole team then analyses against the same thresholds. Nothing is blocked yet, but the standard is agreed and committed. On Pro, install the git hook or the build gate to start blocking files below your chosen threshold. If a large number of files fail, start at legacy or balanced and tighten over time rather than adopting the strictest preset immediately. A gate that fails constantly tends to get disabled.
Gate Preview never writes config or blocks anything on its own. Applying a preset is the only action that changes a file, and it requires an explicit click.