القائمة
Deploy an ObjectScript class or package to IRIS (iris_doc_load, glob-path form), fix compile errors, then run its unit tests (iris_execute_tests) with a total-count check.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review and promote configuration/code drift from a source IRIS environment to a target using the review-before-write iris_env_diff -> iris_env_promote workflow (scoped diff, plan, an explicit user-selected step allowlist, confirmed execute, re-diff verify). Never acts on onlyInTarget warnings -- never deletes a target-only item, in any action.
Resend failed Interoperability messages for a config item using the dry-run-first iris_message_resend workflow — preview the match count before executing, then verify the new headers via iris_production_messages. States the duplication hazard and that resend/resendFiltered are governance-default-disabled writes.
Audit the IRIS instance's security posture: users (default passwords, %All holders), roles, service authentication settings, SSL/TLS configs, and instance auditing status.
Run a full IRIS instance health check (iris_health_check) and interpret every non-ok finding, naming the fixing tool for each one.
Diagnose a slow SQL query using iris_sql_analyze (explain, indexUsage, stats) and recommend a fix — never auto-applies one.
A concise (<=300 word) pre-write checklist distilling the project's ObjectScript conventions ($$$ macros, Quit-in-try/catch, %OnNew/initvalue, no-underscore names, storage sections untouchable, deploy/test discipline).
| name | deploy-and-test-class |
| description | Deploy an ObjectScript class or package to IRIS (iris_doc_load, glob-path form), fix compile errors, then run its unit tests (iris_execute_tests) with a total-count check. |
Target: <classOrPackage>
iris_doc_load with a glob-prefixed path rooted at the local source directory this class/package lives under, e.g. c:/path/to/src/**/<classOrPackage>*.cls — a bare (non-glob) file path mis-maps the class name (Rule #17), so ALWAYS include a directory prefix ending in **/*.cls or **/<ClassName>.cls. Pass compile: true..cls file on disk (never edit generated/compiled output), and re-run step 1. Repeat until iris_doc_load reports zero compile errors.<classOrPackage> names a single class ending in a recognizable test-class pattern (or the user says "just this class"), use level: "class"; if it names a package, use level: "package"; if the user names one specific test method, use level: "method" with target: "ClassName:MethodName".iris_execute_tests with target: "<classOrPackage>" and the chosen level.total against the expected number of test methods (count them from the source file(s) you just deployed, or ask the user). iris_execute_tests can return an early PARTIAL snapshot — all passing, fewer tests than exist (Rule #35) — which looks identical to a genuine green run unless the count is checked.total is short of the expected count, rerun iris_execute_tests (prefer a per-class call when precision matters) before reporting the run as green.