メニュー
Trace a message's flow through an Interoperability production using iris_production_messages, iris_message_diagram, and iris_production_logs for any erroring items.
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.
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.
Diagnose a slow SQL query using iris_sql_analyze (explain, indexUsage, stats) and recommend a fix — never auto-applies one.
| name | trace-message-flow |
| description | Trace a message's flow through an Interoperability production using iris_production_messages, iris_message_diagram, and iris_production_logs for any erroring items. |
Session or header ID to trace: <sessionOrHeaderId>
No namespace specified — omit namespace to use the server's configured default on every call below.
iris_production_messages with sessionId: <sessionOrHeaderId> (traces every message in that session). If the result is empty or the ID does not look like a session ID, retry with headerId: <sessionOrHeaderId> instead — the ID may be a specific message header ID rather than a session ID.iris_message_diagram with sessionIds: [<sessionOrHeaderId>] (use the session ID discovered in step 1, even if you started from a header ID) to render a Mermaid sequence diagram of the same flow — participants, sync vs async calls, request/response pairing, and [ERROR] flags on failed messages.[ERROR] markers), call iris_production_logs filtered by itemName (the erroring config item) and/or type: "Error" to pull the detailed error log entries for that item around the same timeframe.iris_production_control action 'recover', or a data/config fix) but do NOT execute a recovery action without the user's confirmation.