iris-dev

Plugin iris-dev from marketplace iris-agentic-dev in intersystems-community/iris-agentic-dev. Commands read from the repo's manifest — 2 days ago.

Skills (40)

• iris-agentic-dev-setup

  Install the iris-agentic-dev binary, get an IRIS instance running, and register the MCP server. Use when the IRIS tools are missing, when check_config reports disconnected, or when the user asks to set up, install, or connect iris-agentic-dev.

• iris-coverage-run

  Measure ObjectScript line coverage using %Monitor.System.LineByLine. Wraps a %UnitTest.Manager.RunTest() call, collects per-class hit/total counts, prints a coverage table. Prerequisite: iris-coverage-setup (bbsiz=4096, IRIS restarted).

• iris-coverage-setup

  Enable the IRIS line-by-line monitor (bbsiz CPF parameter). Run once per container before measuring ObjectScript test coverage. Verifies $zu(84) is functional and diagnoses build incompatibility.

• pyprod

  Use when creating or modifying InterSystems IRIS interoperability production components in Python — Business Services, Business Processes, Business Operations, Adapters, Messages, or Production definitions.

• ensemble-production

  Manage and observe IRIS Interoperability productions — lifecycle, logs, queues, and message tracing. Covers pyprod Python API, ObjectScript Ens.Director, and MCP tool flow.

• iris-agentic-dev

  Configure, connect, and troubleshoot the iris-agentic-dev MCP server (iris_execute/iris_query/iris_doc/docs_introspect/kb/etc.) against an IRIS container or instance. Use when its tools return IRIS_UNREACHABLE, when pointing it at a new IRIS, or when a connection edit "isn't taking effect." Covers t

• nopws-setup
• iris-ai-hub

  IRIS AI Hub (%AI.* classes, EAP builds): where the upstream docs are and which file covers what, how to check them against the installed build, and the %AI.Agent / %AI.Tool / %AI.ToolSet / ConfigStore / Wallet / MCP server facts measured on 2026.3.0AI builds 139 and 154. Load when building or debugg

• iris-connectivity

  Use when connecting to IRIS from Python, Java, JDBC, ODBC, or any external

• iris-container-graceful-shutdown

  IRIS data persists across container restarts ONLY if IRIS is stopped gracefully before docker stop. Without this, docker stop sends SIGKILL after grace period, leaving the WIJ (write image journal) dirty. Data recovers on next start but takes 30-300s. Load when: stopping IRIS containers, setting up

• iris-cpf-merge

  Use when configuring IRIS containers via CPF merge files (ISC_CPF_MERGE_FILE). Covers CPFPreset patterns, the grongierisc template pattern, how to set a password at first boot (and why a merge line cannot do it safely), and common CPF merge mistakes. Load when: setting up IRIS Docker containers, deb

• iris-devtester

  Use when writing tests that need a live IRIS container, using IRISContainer factory methods, debugging connection failures, or understanding the password reset story. Covers iris-devtester 1.18.0+ patterns: CPF-first password strategy, factory methods, gotchas, and the full connection flow.

• iris-docs

  Look up InterSystems IRIS documentation. Use iris_doc_search for discovery questions and API lookups. Covers the Algolia search recipe, Documatic URL pattern, and when to use docs_introspect vs iris_doc_search vs iris_doc.

• iris-embedded-python

  Use when the user wants to run Python code inside IRIS, call Python libraries from ObjectScript, or use the IRIS Python native API

• iris-linux-docker

  IRIS Docker container volume permissions on Linux. All IRIS editions (community, enterprise, irishealth, ai_hub) run as UID 51773 (irisowner). Bind-mounting a host directory owned by a regular Linux user causes startup crash. Load when IRIS container fails on Linux with iris-main.log error, or when

• iris-mdx

  Use when writing, debugging, or optimizing MDX queries against InterSystems

• iris-objectscript-eval

  Execute, compile, and test ObjectScript code via the objectscript MCP tools. Use when needing to run arbitrary ObjectScript, compile .cls files, or run %UnitTest tests. Prefers MCP tools over docker exec. Falls back to docker exec only when MCP is unavailable.

• iris-pgwire

  Use when connecting to IRIS via the PostgreSQL wire protocol, using psycopg3 or any Postgres-compatible client

• iris-product-features

  Use when asked about IRIS capabilities, products, or features — especially

• iris-query-plans

  Read an IRIS SQL query plan and fix index problems. Use when a query is slow, when a count or search returns fewer rows than the table holds, after adding an Index to a persistent class, or when iris_query(mode="explain") shows "Read master map" where you expected an index. Covers master map vs inde

• iris-sql

  Use when writing, debugging, or optimizing SQL queries in IRIS — table

• iris-vector-ai

  Use when writing any IRIS vector search, embedding, HNSW index, similarity

• iris-vscode-objectscript

  Use when configuring VSCode for ObjectScript development against an IRIS container. Covers the intersystems.servers settings.json config, the critical port 52773 vs 1972 distinction, the working webgateway pattern for enterprise images, three hard-won bugs from the 2026-05-03 session, and how to ver

• iris-windows-iis-setup

  Configure IIS for IRIS installed natively on Windows so iris-agentic-dev can connect

• irishealth-container

  Use when working with irishealth-community (FHIR R4) or irishealth AI Hub containers, OR when setting up VSCode/iris-dev extension against any IRIS container. Covers IRISContainer.health() and ai_hub() factory methods, four hard-won gotchas, the two-container architecture, no-ZPM FHIR setup, and the

• irispython-connector

  Connect Python to IRIS from outside IRIS over TCP — DB-API, SQLAlchemy, and pandas. Covers the port confusion, keyword-arg segfault, FETCH FIRST crash, and type normalization blockers that trip up every first-time user.

• objectscript-coverage

  Measure ObjectScript line coverage using iris_coverage. Use when a user asks about test coverage, coverage reports, or wants to know how well their test suite exercises their code.

• objectscript-debugging

  Captures IRIS diagnostic packets, maps .INT offsets to .CLS source lines, and correlates error logs. Use whenever an IRIS runtime error or compile failure needs to be diagnosed.

• objectscript-fewshot-fixes

  Worked fix examples for the seven most common ObjectScript mistakes AI models make, each as Bug Pattern -> Root Cause -> Fix. Use when fixing an ObjectScript bug involving Quit inside a loop, HTML escaping order, a missing SQL date filter, forward iteration with removal, a missing $IsObject check, p

• objectscript-guardrails

  Use when writing or reviewing any ObjectScript code. Hard gate — 15-item

• objectscript-list-patterns

  ObjectScript %List, %ListOfDataTypes, $LISTBUILD, $LISTTOSTRING, $LISTNEXT

• objectscript-loop-patterns

  ObjectScript For/While loop patterns, $Order iteration, postfix Quit,

• objectscript-mac-routines

  MAC routine syntax — label-based structure, #include, $ZTRAP error traps, extrinsic functions, and Quit vs Return. Use when working with .mac files, legacy CHUI applications, or any pre-class ObjectScript code.

• objectscript-navigation

  Deep codebase discovery using MCP and text tools. Use this to bridge the gap between raw MCP tool data and high-level architectural understanding.

• objectscript-repair

  Perform coordinated fixes across multiple ObjectScript files. Use when a change in one class requires updates in dependent classes (e.g., method signature changes, renames).

• objectscript-review

  Reviews ObjectScript code for common LLM mistakes before presenting to the user

• objectscript-sql-patterns

  ObjectScript embedded SQL, %SQL.Statement, date filtering, NULL handling,

• objectscript-tdd

  Compile-test-fix loop for ObjectScript development. Use when writing or modifying ObjectScript classes.

• objectscript-unit-test

  Generates %UnitTest.TestCase subclasses for ObjectScript classes using live IRIS introspection. Use when asked to write tests for any ObjectScript class or method.

• opencode-introspect

  Read and search opencode session logs from the SQLite DB at ~/.local/share/opencode/opencode.db. Use when you need to review what a session did, assess whether AI work was safe/correct, diagnose a "session wipe", find a specific tool call or output from a past session, or recover the DB after a migr

MCP servers (1)

• iris-dev

  runs: iris-agentic-dev mcp

Hooks (3)

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/compile-hook.sh

• FileChanged

  ${CLAUDE_PLUGIN_ROOT}/scripts/compile-hook.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/version-check.sh

Similar plugins