objectscript-debugging

Diagnose IRIS runtime and compile errors using diagnostic packets and source mapping.

27|10|Updated Apr 21, 2026

Search Tags:#debugging #diagnostics #mapping #error-logs #iris #objectscript

Ready to run

npx skills add https://github.com/intersystems-community/iris-dev --skill objectscript-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: objectscript-debugging
Source: https://github.com/intersystems-community/iris-dev/tree/main/light-skills/skills/objectscript-debugging
Command: npx skills add https://github.com/intersystems-community/iris-dev --skill objectscript-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ground AI debugging in real IRIS signals — compiler errors, messages.log entries, stack traces, and local variable state, rather than guessing from code alone.

Core Features & Use Cases

Capture a diagnostic packet to snapshot the current IRIS error state.
Map .INT offsets to the original .CLS source lines to locate the root cause quickly.
Read recent errors from messages.log and the ^ERRORS global to correlate events and verify fixes.
Reproduce, diagnose, and validate fixes by cross-referencing packets, mappings, and logs to ensure resolution.

Quick Start

Capture a diagnostic packet for the failing IRIS routine, map any referenced offsets to the corresponding source lines, and review logs to correlate issues.

Frequently Asked Questions about objectscript-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose InterSystems IRIS runtime errors using real diagnostic signals?▼

Diagnose IRIS runtime errors by capturing diagnostic packets that snapshot the current error state, then correlating compiler messages, log entries, and stack traces with source lines and local variable state.

How do I map .INT offsets to original .CLS source lines in ObjectScript?▼

Map .INT offsets to original .CLS source lines using diagnostic capture and offset-to-source mapping to locate the root cause of compiler errors quickly during IRIS development.

What is the best way to read recent errors from messages.log and the ^ERRORS global?▼

Read recent errors from messages.log and the ^ERRORS global using error log retrieval to correlate events, cross-reference diagnostic packets, and verify that your runtime fixes are resolved.

Can I use this diagnostic mapping approach in both development and production IRIS environments?▼

Yes, apply diagnostic capture, offset-to-source mapping, and error log retrieval in both development and production IRIS environments to reproduce, diagnose, and validate fixes by cross-referencing packets and logs.

Why does guessing ObjectScript errors from code alone fail to locate the root cause?▼

Guessing ObjectScript errors from code alone fails because it ignores real IRIS signals, whereas grounding AI debugging in actual compiler messages, stack traces, and local state produces actionable guidance.

What should I do if my IRIS compiler messages and log entries do not correlate with the source lines?▼

If compiler messages and log entries do not correlate, capture a fresh diagnostic packet for the failing routine, verify the offset-to-source mapping, and review the ^ERRORS global to cross-reference the issue.