From iris-dev
Maps ObjectScript codebases using MCP tools for symbol anchoring, dependency tracing, and hierarchical exploration. Bridges raw metadata and architectural understanding via iris_symbols and docs_introspect.
How this skill is triggered — by the user, by Claude, or both
Slash command
/iris-dev:objectscript-navigationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides strategies for mapping out ObjectScript codebases using the available MCP tools.
This skill provides strategies for mapping out ObjectScript codebases using the available MCP tools.
Before editing, always locate the Symbol Anchor (the definition of the class or method you intend to change).
iris_symbols(query) — searches the live IRIS namespace by name pattern (supports * wildcards)iris_symbols_local(workspace_path) — parses .cls files on disk via tree-sitter when IRIS is unavailablecontainerName to confirm you are in the correct package.When changing a signature, use Upstream Tracing to find every caller.
docs_introspect(class_name) — fetches the full class definition from %Dictionary, including all methods, parameters, return types, and inheritance chainiris_symbols(query="ClassName.*") — list all members of a classRead tool before modifying. If a method is called from multiple packages, plan all edits before touching any file.ObjectScript heavily uses inheritance (Extends).
Extends list.docs_introspect(class_name) — reveals the full inherited interface including superclass chain.iris_symbols("SuperClass.*") to list members inherited from a superclass.When the model receives a list of symbols from iris_symbols, it should not just "see" a list. It should follow this reasoning:
Package.Class:Method at line 10."docs_introspect('Package.Class') to confirm the method signature and see what it overrides."Package.Class with iris_symbols and Grep to find classes that Extend it."iris_symbols.docs_introspect on any class you did not write before editing it — the live definition may differ from what you can infer from filenames alone.Read to open .cls files on disk when you need line-level context around a symbol.Grep (regex across the workspace) when iris_symbols results are too broad.npx claudepluginhub intersystems-community/iris-agentic-devPerforms coordinated multi-file fixes in ObjectScript projects when a change in one class requires updates in dependent classes (e.g., method signature changes, renames).
Find symbol definitions by name regex, trace call sites with FQN, get symbol file locations, and explore class public APIs using Brokk's searchSymbols, scanUsages, getSymbolLocations, and getClassSkeletons tools.
Routes code intelligence queries to a framework-aware MCP server. Use instead of Read/Grep/Glob for source code exploration, impact analysis, and debugging.