tdyar/objectscript-mac-routines

Validate MAC routine entry, labels, includes, and error handling.

27|10|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/intersystems-community/iris-dev --skill tdyar-objectscript-mac-routines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdyar/objectscript-mac-routines
Source: https://github.com/intersystems-community/iris-dev/tree/main/skills/objectscript-mac-routines
Command: npx skills add https://github.com/intersystems-community/iris-dev --skill tdyar-objectscript-mac-routines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MAC routines are prone to subtle errors that break legacy CHUI and label-based code. This skill provides a preflight discipline that enforces best practices before writing any MAC code, reducing syntax, structural, and runtime issues.

Core Features & Use Cases

  • Hard-gate checks before writing MAC routines, including routine entry style, label indentation, include syntax, and extrinsic call conventions.
  • Guidance for robust error handling with $ZTRAP and safe cross-routine calls, improving code reliability in legacy IRIS projects.
  • Use Case: when maintaining or upgrading .mac files and legacy routines in CHUI-based applications, this skill helps ensure consistent, correct patterns across teams.

Quick Start

Review the MAC routine guidelines and apply the eight pre-write checks to your next .MAC routine before coding.

Frequently Asked Questions about tdyar/objectscript-mac-routines

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

FAQPage Schema
How do I validate MAC routine entry style and label structure in InterSystems IRIS?▼

MAC routine validation enforces routine entry style, label indentation, and include syntax for legacy InterSystems IRIS projects. It applies preflight checks to .mac files to ensure label-based routines maintain correct structural patterns before code is written.

What is the best way to handle error traps and extrinsic calls in legacy .mac files?▼

Handling error traps and extrinsic calls in .mac files requires enforcing $ZTRAP conventions and safe cross-routine references. Preflight validation checks these patterns to prevent subtle runtime errors in legacy CHUI-based applications.

How do I run preflight checks on MAC routines before writing new InterSystems ObjectScript code?▼

Preflight checks on MAC routines are applied by reviewing eight standard guidelines covering routine entry, include syntax, and cross-routine references. Developers apply these checks to .mac files before coding to reduce syntax and structural issues.

Does this MAC routine validation work for CHUI-style workflows and legacy IRIS projects?▼

MAC routine validation is designed specifically for legacy InterSystems IRIS projects involving .mac files and CHUI-style workflows. It ensures consistent, standards-compliant code patterns across teams maintaining or upgrading legacy label-based routines.

Why do my legacy MAC routines break during maintenance and code reviews?▼

Legacy MAC routines break due to subtle errors in label structure, include syntax, and extrinsic call conventions. Preflight validation catches these structural and runtime issues during maintenance or code reviews before they impact legacy CHUI applications.