From iris-dev
Compile-test-fix loop for ObjectScript development. Guides writing, compiling, and testing ObjectScript classes with common error fixes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/iris-dev:objectscript-tddThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Close the feedback loop: write → compile → fix errors → run tests → fix failures → done.
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 |
npx claudepluginhub intersystems-community/iris-agentic-devUploads and compiles ObjectScript .cls files to InterSystems IRIS via Atelier REST, returning structured compile errors for immediate fixing.
Diagnoses and fixes test failures, build errors, runtime errors, environment issues, and more by categorizing errors and applying targeted strategies with minimal context.
Mentally executes code, skills, commands, configs line-by-line with concrete values to find bugs, logic errors, edge cases, contract violations, AI hallucinations. Verifies external calls using tools.