Iris Code

Report code-health findings for a file, folder, or workspace: every rule that fired, each with its line, severity, and a stable id you can pass to iris_fix_safe. Also reports which files import each checked file, the project health score, and the gate threshold. Use this before editing a file to see what else to re-check, or to answer whether code is ready to commit or push. One file and its direct importers are Free. A directory captures a project review using the current local allowance. Pass its inspection.evidence_id to reopen captured findings without rescanning. (Free file checks; signed-in project reviews use the current workspace allowance)

Report known vulnerabilities for this project's dependencies from OSV: severity, confidence, and the nearest fixed version, per package. Saved reports stay readable without refreshing. A fresh audit needs sign-in and network consent, and uses one local project action on Free. no_cache explicitly refreshes provider data. (Saved reports are Free; fresh audits use the current workspace allowance)

Report whether one package is safe to add, BEFORE you add or upgrade it as a dependency: whether the version that would install has a known vulnerability, is reported malicious, is yanked, deprecated or a prerelease, or was published so recently it breaks this project's policy - and which version to install instead. Call this before every install command you run and before editing a manifest to add or bump a package. Pass ecosystem (npm, python, cargo, go, rubygems, nuget, maven), name, and optionally version (exact, a range, or a tag). If blocks is true, do not install that version; use suggestedCommand. Needs allow_network: true the first time on a machine. (Free)

Report the rules this project actually enforces, as Iris Code resolves them: thresholds, scoring weights, gate limits, naming policy, and which folder is being analysed and why. Use this before suggesting a change, so your advice matches what the pre-push hook and CI block on rather than a general convention. (Free)

Explain a finding: the rule behind it, why it fired here, and what would satisfy it. Use this when you need the cause rather than the label, so a fix addresses the rule instead of silencing it. (Saved explanations included; fresh file explanations require Pro)

Preview, then apply, only the changes Iris Code can prove safe: merge compatible imports, remove unused import bindings or statements, remove isolated debug statements, or remove literal-only unused variables, including proved multiline ranges. console.error and unused functions are never auto-fixed. Previews by default and returns a preview_token that a later apply must echo back; changed source requires a fresh preview. Refuses per finding with a reason: anything needing a name or a judgement stays your work, and a secret is never auto-fixed. One file is Free; folder and workspace scope need Pro. (Free)

Report whether this project's configured quality gate would pass, and which files fail which rule. This is the same decision the pre-push hook and CI make, so use it to answer whether a push or build would be blocked. (Saved gate previews included; fresh enforcement requires paid access to this workspace)

Report a refactor plan for a source file: proved mechanical fixes first, then located suggestions ordered by risk, with destinations from project conventions. Returns a baseline_id held in this session. Apply fixes, preserve behavior and exports, and verify after each move. One planned file remains Free. Fresh folder/workspace plans require sign-in and use one local project action on Free; paid local access is unmetered. The earned project baseline is saved locally. (Free)

Report database tables, columns and relations read from repository schema code, with unresolved references and conflicts disclosed. Before writing a query, migration or model change, call this to get the real table and column names instead of guessing. Schema structure and usage for one named table are Free. Pass a saved project evidence_id for aggregate usage without rescanning. (Free)

Report verification of a refactor against the session baseline_id or git HEAD. Discovers changed and new workspace files even if omitted from files. Rejects packing, broken imports, new cycles, removed imported exports and new findings, and reports code-line movement, health scores, disabled checks and a correction instruction. Never supply before content. One-file verification remains Free. Verification of an earned multi-file baseline uses no additional action, including after allowance exhaustion; never supply a before-source snapshot. (Free)