Hooks and CI
Stop changes that fail your rules.
The editor, CLI, hooks and CI read the same committed .irisconfig.json. Pro enforcement can refuse a push or fail a build when the configured gate does not pass.
What it does
Turn a written standard into a pass or fail.
A gate compares scan results with the limits in .irisconfig.json. Those limits can include the health score and separate constraints on findings. Clearing the score alone does not mean every gate rule passes.
Gate Preview lets you inspect built-in presets without blocking anything. With Pro, a pre-push hook can refuse a push and the CI gate can fail a pipeline when the configured rules do not pass. Both read the project's committed configuration.
- Compare built-in presets in Gate Preview before enabling enforcement.
- Choose thresholds, weights and enforcement limits for the repository.
- Run the gate locally and in CI against the same project configuration.
Why use it
A standard matters at the point a change is accepted.
Feedback gives you a chance to fix a problem. Enforcement defines what happens when a configured limit still fails.
- Choose limits with evidence
- Preview presets before enabling a gate. You can inspect the repository against a standard before deciding which limits fit it.
- Make the decision repeatable
- Commit .irisconfig.json with the project. The editor, CLI, hooks and CI can apply the same explicit rules instead of relying on each developer's interpretation.
- Keep a check beyond the local machine
- A local hook can be bypassed with git push --no-verify. Running the gate in CI gives the pipeline a configured check even when the local hook is skipped.
How to use it
Preview first. Enforce deliberately.
Gate Preview is Free and read-only. Custom limits are available when signed in. Pre-push enforcement, supported build hooks and the CI gate require applicable paid access.
Inspect Gate Preview
Open Preview Gate at the bottom of the editor's File view and compare the built-in presets. This does not install a hook or block a push.
ResultYou can consider the gate result before enabling enforcement.
Choose and commit the configuration
Use a preset or sign in to choose custom limits in .irisconfig.json. Validate the configuration before committing it with the repository.
Validate the project configuration iris config validateResultThe repository contains a shared standard that the tools can read.
Install the pre-push hook
Activate Pro and install the Git hook from the project directory. On a push, read any failing rule, fix the finding or deliberately revise the configuration.
Install the Pro pre-push hook iris hook git installResultThe local pre-push check can refuse changes that fail the configured gate.
Run the same gate in CI
Add the gate to your pipeline with Pro activation configured for the runner. Keep the committed project configuration available to that step.
CI quality gate iris gate . --format githubResultThe CI step fails when the configured gate fails.
The capabilities, in detail.
- AI-assisted presetFree
- Stricter explicit limits for teams reviewing AI-assisted code at volume, without imposing a team-specific naming style.
- Dashboard config syncFree
- Pick a preset on the web and push it straight to your editor with a diff preview.
- Gate Preview drilldownPro
- Failing file names, scores, and warning pills inside each preset row.
- Custom enforcement limitsPro
- Block on secret count, complexity ceiling, file size, or smell density.
- Custom scoring weightsPro
- Tune how much each finding type costs the health score - make secrets fatal and TODOs cosmetic, or the reverse.
- Config StudioPro
- A visual editor for your full config, synced back to your editor - no hand-editing JSON.
- Per-language overridesPro
- Set thresholds and per-file gate caps independently for TypeScript, JavaScript, Go, Python, Ruby, C#, Java, and Rust; Vue and Svelte scripts follow their matching TS or JS policy.
- Git pre-push hookPro
- Block any push that falls below your health threshold.
- Build hookPro
- Stop JS, Go, Python, and Ruby builds before they run.
- Push-blocked counterPro
- Monthly and total pushes blocked, plus health delta since Pro.
- Slack notificationsFree
- Set one CI secret and an existing gate step posts its result to Slack. No pipeline edit and no flag. The message is built and sent by your own runner, carries file paths, scores and counts only, and never passes through an Iris Code server. Setup guide.
Choose your scope
What's included.
- Free
- Gate Preview is a read-only check on the built-in presets. It does not install a hook or block a push.
- Pro and Teams
- Signed-in users can choose custom limits. Pro adds the pre-push hook, supported build hooks and the CI gate.
Know the boundary
What it doesn't promise.
The gate applies the configured rules. A passing score is not a security certification; other gate rules can still fail.
Start here.
Preview the gate first. Set up the pre-push hook and CI once you have chosen limits that fit the repository.