From iris-dev
Guides compile-test-fix loop for ObjectScript classes in IRIS, including compilation commands, common error fixes, and unit test runs. Use when writing or modifying classes.
npx claudepluginhub intersystems-community/iris-devThis skill uses the workspace's default tool permissions.
Close the feedback loop: write → compile → fix errors → run tests → fix failures → done.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Close the feedback loop: write → compile → fix errors → run tests → fix failures → done.
Use the objectscript MCP tool when available (check /mcp):
iris_compile(target="MyPackage/MyClass.cls", namespace="USER")
Fallback when MCP is unavailable:
iris session IRIS -U USER "Do $System.OBJ.Load(\"<ClassName>.cls\",\"ck\")"
Never present code to the user that hasn't compiled. If you can't compile (no IRIS access), flag this explicitly:
⚠️ No IRIS connection available — code is unverified. Recommend compiling before use.
| Error | Cause | Fix |
|---|---|---|
QUIT argument not allowed | Quit <val> inside TRY/CATCH or loop | Change to Return <val> |
Expected a compilable class | Missing Class keyword or malformed header | Check class declaration line |
Method does not exist | Intra-class call without .. | Add .. prefix |
<UNDEFINED> at runtime | Variable used before SET | Initialize variable before use |
Expected white space | Missing space after command keyword | Add space: Set x=1 not Setx=1 |