メニュー
Provision a new IRIS project environment: two databases, a namespace, a user, and a web application — verifying each step before the next, with rollback notes.
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 | provision-project-environment |
| description | Provision a new IRIS project environment: two databases, a namespace, a user, and a web application — verifying each step before the next, with rollback notes. |
Project: <projectName>
Verify EACH step succeeded (inspect the tool result) before proceeding to the next. If any step fails partway through, roll back the steps already completed (see the rollback note after each step) rather than leaving a half-provisioned environment.
iris_database_manage action 'create' with name: "<projectName>DATA" and a directory for the DATA database. Rollback: iris_database_manage action 'delete' with name: "<projectName>DATA".iris_database_manage action 'create' with name: "<projectName>CODE" and a directory for the CODE database. Rollback: iris_database_manage action 'delete' with name: "<projectName>CODE".iris_namespace_manage action 'create' with name: "<projectName>", dataDatabase: "<projectName>DATA", codeDatabase: "<projectName>CODE". Rollback: iris_namespace_manage action 'delete' with name: "<projectName>", then undo steps 1-2.iris_user_manage action 'create' with a name and password for the project's service/developer account, and namespace: "<projectName>" as its default namespace. Rollback: iris_user_manage action 'delete' with the same name.iris_webapp_manage action 'create' with a name starting with '/' (e.g. '/api/'), namespace: "<projectName>", and (if applicable) a dispatchClass. Note: creating a web app does NOT notify the CSP gateway — it requires saving through the Management Portal or a gateway restart to become active. Rollback: iris_webapp_manage action 'delete' with the same name.