@cxtms/cx-schema 1.6.7 → 1.7.0

package/.claude/skills/cx-core/SKILL.md

@@ -14,10 +14,10 @@ The CLI can authenticate against CX environments and manage server resources. Au
 
 ```bash
 # Login to a CX environment (OAuth2 + PKCE — opens browser)
-npx cx-cli login https://tms-v3-dev.usatrt.com
+npx cxtms login https://tms-v3-dev.usatrt.com
 
 # Logout from current session
-npx cx-cli logout
+npx cxtms logout
 ```
 
 The session is stored at `~/.cxtms/<project-dir>/.session.json`, scoped by project directory name. Each project gets its own server session. The CLI auto-refreshes expired tokens.
@@ -28,16 +28,16 @@ For CI/CD or headless environments, use Personal Access Tokens instead of intera
 
 ```bash
 # Check PAT status and setup instructions
-npx cx-cli pat setup
+npx cxtms pat setup
 
 # Create a new PAT token (requires OAuth login first)
-npx cx-cli pat create "my-ci-token"
+npx cxtms pat create "my-ci-token"
 
 # List active PAT tokens
-npx cx-cli pat list
+npx cxtms pat list
 
 # Revoke a PAT token
-npx cx-cli pat revoke <tokenId>
+npx cxtms pat revoke <tokenId>
 ```
 
 After creating a PAT, add to `.env` in your project root:
@@ -52,16 +52,16 @@ When `CXTMS_AUTH` is set, the CLI skips OAuth and uses the PAT token directly. `
 
 ```bash
 # List organizations on the server
-npx cx-cli orgs list
+npx cxtms orgs list
 
 # Select an organization interactively
-npx cx-cli orgs select
+npx cxtms orgs select
 
 # Set active organization by ID
-npx cx-cli orgs use <orgId>
+npx cxtms orgs use <orgId>
 
 # Show current context (server, org, app)
-npx cx-cli orgs use
+npx cxtms orgs use
 ```
 
 The active org is cached in the session file and used by all server commands. Override with `--org <id>`.
@@ -77,14 +77,14 @@ Server commands resolve the target session in this order:
 
 ```bash
 # Publish all modules and workflows from current project
-npx cx-cli publish
+npx cxtms publish
 
 # Publish only a specific feature directory
-npx cx-cli publish --feature billing
-npx cx-cli publish billing
+npx cxtms publish --feature billing
+npx cxtms publish billing
 
 # Publish with explicit org ID
-npx cx-cli publish --org 42
+npx cxtms publish --org 42
 ```
 
 Validates all YAML files first, then pushes modules and workflows to the server. Skips files with validation errors and reports results.
@@ -106,7 +106,7 @@ When creating new modules or workflows, always place them under the correct feat
 - `features/<feature_name>/modules/<name>-module.yaml`
 - `features/<feature_name>/workflows/<name>.yaml`
 
-Use `--feature <feature_name>` with `cx-cli create` to automatically place files in the correct location.
+Use `--feature <feature_name>` with `cxtms create` to automatically place files in the correct location.
 
 ## Entity Field Reference
 

package/.claude/skills/cx-module/SKILL.md

@@ -6,28 +6,28 @@ argument-hint: <description of what to build>
 
 You are a CargoXplorer module YAML builder. You generate schema-valid YAML for CX app modules — UI screens, forms, data grids, routes, and components. All output must conform to the JSON schemas in `.cx-schema/`.
 
-**IMPORTANT — use `cx-cli` for all module operations:**
-- **Scaffold**: `npx cx-cli create module <name> --template <template>` — generates a schema-valid YAML file. ALWAYS run this first, then read the generated file, then customize. Do NOT write YAML from scratch or copy templates manually.
-- **Scaffold with fields**: `npx cx-cli create module <name> --template <template> --options '<json>'`
-- **Validate**: `npx cx-cli <file.yaml>` — run after every change
-- **Schema lookup**: `npx cx-cli schema <component>` — e.g., `cx-cli schema form`, `cx-cli schema dataGrid`
-- **Examples**: `npx cx-cli example <component>` — show example YAML
-- **List schemas**: `npx cx-cli list`
-- **Extract**: `npx cx-cli extract <source> <component> --to <target>` — move components between modules
-- **Feature folder**: `npx cx-cli create module <name> --template <template> --feature <feature-name>`
-- **Deploy to server**: `npx cx-cli appmodule deploy <file.yaml>` — creates or updates module on the CX server
-- **Undeploy from server**: `npx cx-cli appmodule undeploy <appModuleId>` — removes a module by UUID
-- **Publish all**: `npx cx-cli publish [--feature <name>]` — push all modules and workflows to the server
+**IMPORTANT — use `cxtms` for all module operations:**
+- **Scaffold**: `npx cxtms create module <name> --template <template>` — generates a schema-valid YAML file. ALWAYS run this first, then read the generated file, then customize. Do NOT write YAML from scratch or copy templates manually.
+- **Scaffold with fields**: `npx cxtms create module <name> --template <template> --options '<json>'`
+- **Validate**: `npx cxtms <file.yaml>` — run after every change
+- **Schema lookup**: `npx cxtms schema <component>` — e.g., `cxtms schema form`, `cxtms schema dataGrid`
+- **Examples**: `npx cxtms example <component>` — show example YAML
+- **List schemas**: `npx cxtms list`
+- **Extract**: `npx cxtms extract <source> <component> --to <target>` — move components between modules
+- **Feature folder**: `npx cxtms create module <name> --template <template> --feature <feature-name>`
+- **Deploy to server**: `npx cxtms appmodule deploy <file.yaml>` — creates or updates module on the CX server
+- **Undeploy from server**: `npx cxtms appmodule undeploy <appModuleId>` — removes a module by UUID
+- **Publish all**: `npx cxtms publish [--feature <name>]` — push all modules and workflows to the server
 
 ## Generation Workflow
 
 ### Step 1: Scaffold via CLI — MANDATORY
 
-**You MUST run `cx-cli create module` to generate the initial file.** Do not skip this step. Do not write YAML from scratch. Do not read template files and copy them manually. The CLI generates correct UUIDs, file paths, and structure.
+**You MUST run `cxtms create module` to generate the initial file.** Do not skip this step. Do not write YAML from scratch. Do not read template files and copy them manually. The CLI generates correct UUIDs, file paths, and structure.
 
 ```bash
-npx cx-cli create module <name> --template <template>
-npx cx-cli create module <name> --template <template> --options '<json>'
+npx cxtms create module <name> --template <template>
+npx cxtms create module <name> --template <template> --options '<json>'
 ```
 
 | Template | Use Case |
@@ -55,7 +55,7 @@ npx cx-cli create module <name> --template <template> --options '<json>'
 ### Step 4: Validate
 
 ```bash
-npx cx-cli <generated-file.yaml>
+npx cxtms <generated-file.yaml>
 ```
 
 ---
@@ -67,7 +67,7 @@ Customize generated modules at scaffold time with `--options`. Accepts inline JS
 ### Field Array Format (all templates)
 
 ```bash
-npx cx-cli create module "Tariff" --template grid --options '[
+npx cxtms create module "Tariff" --template grid --options '[
   {"name": "code", "type": "text", "label": "Tariff Code", "required": true},
   {"name": "rate", "type": "number", "label": "Rate %"},
   {"name": "effectiveDate", "type": "date"},
@@ -78,7 +78,7 @@ npx cx-cli create module "Tariff" --template grid --options '[
 ### Object Format (with entityName)
 
 ```bash
-npx cx-cli create module "Country" --template select --options '{
+npx cxtms create module "Country" --template select --options '{
   "entityName": "Country",
   "fields": [
     {"name": "countryCode", "type": "text", "label": "Country Code"},
@@ -113,8 +113,8 @@ npx cx-cli create module "Country" --template select --options '{
 Move or copy a component (and its routes) from one module into another. Useful for splitting large modules or sharing components.
 
 ```bash
-cx-cli extract <source-file> <component-name> --to <target-file>
-cx-cli extract <source-file> <component-name> --to <target-file> --copy
+cxtms extract <source-file> <component-name> --to <target-file>
+cxtms extract <source-file> <component-name> --to <target-file> --copy
 ```
 
 ### Flags
@@ -130,13 +130,13 @@ cx-cli extract <source-file> <component-name> --to <target-file> --copy
 
 ```bash
 # Move a component to a new file (creates module scaffold automatically)
-npx cx-cli extract modules/orders.yaml Orders/CreateItem --to modules/order-create.yaml
+npx cxtms extract modules/orders.yaml Orders/CreateItem --to modules/order-create.yaml
 
 # Copy a component (source unchanged, target gets higher priority)
-npx cx-cli extract modules/orders.yaml Orders/CreateItem --to modules/order-create.yaml --copy
+npx cxtms extract modules/orders.yaml Orders/CreateItem --to modules/order-create.yaml --copy
 
 # Extract to an existing module
-npx cx-cli extract modules/main.yaml Dashboard --to modules/dashboard.yaml
+npx cxtms extract modules/main.yaml Dashboard --to modules/dashboard.yaml
 ```
 
 ### New Target Scaffold
@@ -149,7 +149,7 @@ When the target file doesn't exist, a new module is created with:
 ### Workflow
 1. Run `extract` to move the component
 2. Manually move any related permissions/entities if needed
-3. Validate both files: `npx cx-cli <source>` and `npx cx-cli <target>`
+3. Validate both files: `npx cxtms <source>` and `npx cxtms <target>`
 
 ---
 
@@ -401,26 +401,26 @@ Reusable select components (e.g., `Countries/Select`, `Ports/Select`) follow thi
 
 ```bash
 # Deploy a module YAML to the server (creates or updates)
-npx cx-cli appmodule deploy modules/my-module.yaml
+npx cxtms appmodule deploy modules/my-module.yaml
 
 # Deploy with explicit org ID
-npx cx-cli appmodule deploy modules/my-module.yaml --org 42
+npx cxtms appmodule deploy modules/my-module.yaml --org 42
 
 # Undeploy an app module by UUID
-npx cx-cli appmodule undeploy <appModuleId>
+npx cxtms appmodule undeploy <appModuleId>
 
 # Publish all modules and workflows (validates first)
-npx cx-cli publish
-npx cx-cli publish --feature billing
+npx cxtms publish
+npx cxtms publish --feature billing
 ```
 
-Deploy reads `module.appModuleId` from the YAML, queries the server, and creates or updates accordingly. Requires an active session (`cx-cli login` or PAT token — see cx-core skill).
+Deploy reads `module.appModuleId` from the YAML, queries the server, and creates or updates accordingly. Requires an active session (`cxtms login` or PAT token — see cx-core skill).
 
 ---
 
 # Generation Rules
 
-1. **Always scaffold via `cx-cli create module` first** — never write YAML from scratch, never copy templates manually
+1. **Always scaffold via `cxtms create module` first** — never write YAML from scratch, never copy templates manually
 2. **Use localized strings** `{ en-US: "..." }` for all user-visible text
 3. **Follow naming conventions**:
    - Module names: PascalCase (e.g., `WarehouseLocations`)
@@ -433,4 +433,4 @@ Deploy reads `module.appModuleId` from the YAML, queries the server, and creates
 7. **DataGrid options** requires ALL properties: query, rootEntityName, entityKeys, navigationType, enableDynamicGrid, enableViews, enableSearch, enablePagination, enableColumns, enableFilter, defaultView, onRowClick
 8. **Form component** requires `validationSchema` in props
 9. **Do not change `appModuleId` or `filePath`** — set correctly by CLI scaffold
-10. **Always validate** the final YAML: `npx cx-cli <file.yaml>`
+10. **Always validate** the final YAML: `npx cxtms <file.yaml>`

package/.claude/skills/cx-workflow/SKILL.md

@@ -6,28 +6,28 @@ argument-hint: <description of what to build>
 
 You are a CargoXplorer workflow YAML builder. You generate schema-valid YAML for CX workflows — both standard process workflows (activities, steps, triggers) and Flow state machine workflows (entity lifecycle, states, transitions). All output must conform to the JSON schemas in `.cx-schema/`.
 
-**IMPORTANT — use `cx-cli` for all workflow operations:**
-- **Scaffold**: `npx cx-cli create workflow <name> --template <template>` — generates a schema-valid YAML file. ALWAYS run this first, then read the generated file, then customize. Do NOT write YAML from scratch or copy templates manually.
-- **Validate**: `npx cx-cli <file.yaml>` — run after every change
-- **Schema lookup**: `npx cx-cli schema <task>` — e.g., `cx-cli schema graphql`, `cx-cli schema foreach`, `cx-cli schema action-event`. Schema names use kebab-case file names. Case-insensitive: `ActionEvent` resolves to `action-event`.
-- **Examples**: `npx cx-cli example <task>` — show example YAML for a task
-- **List schemas**: `npx cx-cli list --type workflow` — shows all available task schemas in the Tasks section
-- **Feature folder**: `npx cx-cli create workflow <name> --template <template> --feature <feature-name>`
-- **Deploy to server**: `npx cx-cli workflow deploy <file.yaml>` — creates or updates workflow on the CX server
-- **Undeploy from server**: `npx cx-cli workflow undeploy <workflowId>` — removes a workflow by UUID
-- **Execute**: `npx cx-cli workflow execute <workflowId|file.yaml> [--vars '<json>']` — trigger a workflow execution
-- **List logs**: `npx cx-cli workflow logs <workflowId|file.yaml> [--from YYYY-MM-DD] [--to YYYY-MM-DD]` — list executions with log availability
-- **Download log**: `npx cx-cli workflow log <executionId> [--json] [--console] [--output <file>]` — download execution log
-- **Publish all**: `npx cx-cli publish [--feature <name>]` — push all modules and workflows to the server
+**IMPORTANT — use `cxtms` for all workflow operations:**
+- **Scaffold**: `npx cxtms create workflow <name> --template <template>` — generates a schema-valid YAML file. ALWAYS run this first, then read the generated file, then customize. Do NOT write YAML from scratch or copy templates manually.
+- **Validate**: `npx cxtms <file.yaml>` — run after every change
+- **Schema lookup**: `npx cxtms schema <task>` — e.g., `cxtms schema graphql`, `cxtms schema foreach`, `cxtms schema action-event`. Schema names use kebab-case file names. Case-insensitive: `ActionEvent` resolves to `action-event`.
+- **Examples**: `npx cxtms example <task>` — show example YAML for a task
+- **List schemas**: `npx cxtms list --type workflow` — shows all available task schemas in the Tasks section
+- **Feature folder**: `npx cxtms create workflow <name> --template <template> --feature <feature-name>`
+- **Deploy to server**: `npx cxtms workflow deploy <file.yaml>` — creates or updates workflow on the CX server
+- **Undeploy from server**: `npx cxtms workflow undeploy <workflowId>` — removes a workflow by UUID
+- **Execute**: `npx cxtms workflow execute <workflowId|file.yaml> [--vars '<json>']` — trigger a workflow execution
+- **List logs**: `npx cxtms workflow logs <workflowId|file.yaml> [--from YYYY-MM-DD] [--to YYYY-MM-DD]` — list executions with log availability
+- **Download log**: `npx cxtms workflow log <executionId> [--json] [--console] [--output <file>]` — download execution log
+- **Publish all**: `npx cxtms publish [--feature <name>]` — push all modules and workflows to the server
 
 ## Generation Workflow
 
 ### Step 1: Scaffold via CLI — MANDATORY
 
-**You MUST run `cx-cli create workflow` to generate the initial file.** Do not skip this step. Do not write YAML from scratch. Do not read template files and copy them manually. The CLI generates correct UUIDs, file paths, and structure.
+**You MUST run `cxtms create workflow` to generate the initial file.** Do not skip this step. Do not write YAML from scratch. Do not read template files and copy them manually. The CLI generates correct UUIDs, file paths, and structure.
 
 ```bash
-npx cx-cli create workflow <name> --template <template>
+npx cxtms create workflow <name> --template <template>
 ```
 
 | Template | Use Case |
@@ -77,7 +77,7 @@ npx cx-cli create workflow <name> --template <template>
 ### Step 4: Validate
 
 ```bash
-npx cx-cli <generated-file.yaml>
+npx cxtms <generated-file.yaml>
 ```
 
 ### File Placement
@@ -319,27 +319,27 @@ Implicit variable: `iteration` (zero-based).
 
 ```bash
 # Push a workflow YAML to the server (creates or updates)
-npx cx-cli workflow deploy workflows/my-workflow.yaml
+npx cxtms workflow deploy workflows/my-workflow.yaml
 
 # Delete a workflow by UUID
-npx cx-cli workflow undeploy <workflowId>
+npx cxtms workflow undeploy <workflowId>
 
 # Publish all modules and workflows (validates first)
-npx cx-cli publish
-npx cx-cli publish --feature billing
+npx cxtms publish
+npx cxtms publish --feature billing
 ```
 
-Deploy reads `workflow.workflowId` from the YAML, queries the server, and creates or updates accordingly. Requires an active session (`cx-cli login` or PAT token — see cx-core skill).
+Deploy reads `workflow.workflowId` from the YAML, queries the server, and creates or updates accordingly. Requires an active session (`cxtms login` or PAT token — see cx-core skill).
 
 ### Execute
 
 ```bash
 # Execute a workflow by UUID or YAML file
-npx cx-cli workflow execute <workflowId>
-npx cx-cli workflow execute workflows/my-workflow.yaml
+npx cxtms workflow execute <workflowId>
+npx cxtms workflow execute workflows/my-workflow.yaml
 
 # Pass input variables as JSON
-npx cx-cli workflow execute <workflowId> --vars '{"city": "London", "count": 5}'
+npx cxtms workflow execute <workflowId> --vars '{"city": "London", "count": 5}'
 ```
 
 Returns execution result including `executionId`, `isAsync`, `outputs` (for Sync workflows).
@@ -348,25 +348,25 @@ Returns execution result including `executionId`, `isAsync`, `outputs` (for Sync
 
 ```bash
 # List executions with log availability (sorted desc by date)
-npx cx-cli workflow logs <workflowId|file.yaml>
+npx cxtms workflow logs <workflowId|file.yaml>
 
 # Filter by date range
-npx cx-cli workflow logs <workflowId> --from 2026-01-01 --to 2026-01-31
+npx cxtms workflow logs <workflowId> --from 2026-01-01 --to 2026-01-31
 
 # Download a specific execution log (saves to temp dir by default)
-npx cx-cli workflow log <executionId>
+npx cxtms workflow log <executionId>
 
 # Save to specific file
-npx cx-cli workflow log <executionId> --output mylog.txt
+npx cxtms workflow log <executionId> --output mylog.txt
 
 # Print to stdout
-npx cx-cli workflow log <executionId> --console
+npx cxtms workflow log <executionId> --console
 
 # Download JSON log (richer data: inputs, outputs, timing, metadata)
-npx cx-cli workflow log <executionId> --json
+npx cxtms workflow log <executionId> --json
 
 # JSON log to stdout
-npx cx-cli workflow log <executionId> --json --console
+npx cxtms workflow log <executionId> --json --console
 ```
 
 `workflow logs` shows a table with execution status, date, duration, user, and log availability indicators (filled/empty circle). `workflow log` downloads the actual log content from the server (gzip-compressed S3 URLs).
@@ -382,7 +382,7 @@ npx cx-cli workflow log <executionId> --json --console
 
 ## Generation Rules
 
-1. **Always scaffold via `cx-cli create workflow` first** — never write YAML from scratch, never copy templates manually
+1. **Always scaffold via `cxtms create workflow` first** — never write YAML from scratch, never copy templates manually
 2. **Naming conventions**: step names PascalCase, variables camelCase, states PascalCase, transitions camelCase
 3. **Template expressions** use `{{ expression }}` — NCalc conditions use `[variable]`
 4. **Do not change `workflowId` or `filePath`** — set correctly by CLI scaffold
@@ -390,4 +390,4 @@ npx cx-cli workflow log <executionId> --json --console
 6. **Flow workflows** require `entity`, `states`, `transitions` (no `activities`)
 7. **Entity triggers** require `entityName` and `eventType`
 8. **Always use null-safe `?`** on variable paths — `Activity?.Step?.output?` — unless referencing guaranteed system variables (see Variable References section)
-9. **Always validate** the final YAML: `npx cx-cli <file.yaml>`
+9. **Always validate** the final YAML: `npx cxtms <file.yaml>`

package/README.md

@@ -29,19 +29,19 @@ npm install @cxtms/cx-schema
 
 ```bash
 # Initialize a new project
-npx cx-cli init
+npx cxtms init
 
 # Create a new module
-npx cx-cli create module orders
+npx cxtms create module orders
 
 # Create a new workflow
-npx cx-cli create workflow invoice-processor
+npx cxtms create workflow invoice-processor
 
 # Validate files
-npx cx-cli modules/*.yaml workflows/*.yaml
+npx cxtms modules/*.yaml workflows/*.yaml
 
 # Generate validation report
-npx cx-cli report modules/*.yaml --report report.html
+npx cxtms report modules/*.yaml --report report.html
 ```
 
 ## CLI Commands
@@ -51,14 +51,14 @@ npx cx-cli report modules/*.yaml --report report.html
 Validate YAML file(s) against JSON Schema definitions.
 
 ```bash
-cx-cli [files...]
-cx-cli validate [files...]
+cxtms [files...]
+cxtms validate [files...]
 
 # Examples
-cx-cli modules/orders-module.yaml
-cx-cli modules/*.yaml workflows/*.yaml
-cx-cli --verbose modules/orders-module.yaml
-cx-cli --format json modules/orders-module.yaml
+cxtms modules/orders-module.yaml
+cxtms modules/*.yaml workflows/*.yaml
+cxtms --verbose modules/orders-module.yaml
+cxtms --format json modules/orders-module.yaml
 ```
 
 ### init
@@ -66,7 +66,7 @@ cx-cli --format json modules/orders-module.yaml
 Initialize a new CX project with configuration files.
 
 ```bash
-cx-cli init
+cxtms init
 ```
 
 Creates:
@@ -81,11 +81,11 @@ Creates:
 Create a new module or workflow from template.
 
 ```bash
-cx-cli create <type> <name>
+cxtms create <type> <name>
 
 # Examples
-cx-cli create module orders
-cx-cli create workflow invoice-generator
+cxtms create module orders
+cxtms create workflow invoice-generator
 ```
 
 Generated files include:
@@ -98,12 +98,12 @@ Generated files include:
 Generate validation report for multiple files.
 
 ```bash
-cx-cli report [files...] --report <output-file>
+cxtms report [files...] --report <output-file>
 
 # Examples
-cx-cli report modules/*.yaml --report report.html
-cx-cli report workflows/*.yaml --report report.md
-cx-cli report modules/*.yaml workflows/*.yaml --report results.json
+cxtms report modules/*.yaml --report report.html
+cxtms report workflows/*.yaml --report report.md
+cxtms report modules/*.yaml workflows/*.yaml --report results.json
 ```
 
 Report formats (auto-detected from extension):
@@ -116,13 +116,13 @@ Report formats (auto-detected from extension):
 Display the JSON Schema definition for a component or task.
 
 ```bash
-cx-cli schema <name>
+cxtms schema <name>
 
 # Examples
-cx-cli schema form
-cx-cli schema dataGrid
-cx-cli schema workflow
-cx-cli schema foreach
+cxtms schema form
+cxtms schema dataGrid
+cxtms schema workflow
+cxtms schema foreach
 ```
 
 ### example
@@ -130,11 +130,11 @@ cx-cli schema foreach
 Show example YAML for a component or task.
 
 ```bash
-cx-cli example <name>
+cxtms example <name>
 
 # Examples
-cx-cli example form
-cx-cli example workflow
+cxtms example form
+cxtms example workflow
 ```
 
 ### list
@@ -142,9 +142,9 @@ cx-cli example workflow
 List all available schemas for validation.
 
 ```bash
-cx-cli list
-cx-cli list --type module
-cx-cli list --type workflow
+cxtms list
+cxtms list --type module
+cxtms list --type workflow
 ```
 
 ## CLI Options
@@ -298,11 +298,11 @@ Generated workflows include:
 ```yaml
 - name: Validate YAML files
   run: |
-    npx cx-cli --format compact modules/*.yaml workflows/*.yaml
+    npx cxtms --format compact modules/*.yaml workflows/*.yaml
 
 - name: Generate validation report
   run: |
-    npx cx-cli report modules/*.yaml workflows/*.yaml --report validation-report.html
+    npx cxtms report modules/*.yaml workflows/*.yaml --report validation-report.html
 
 - name: Upload report
   uses: actions/upload-artifact@v3
@@ -316,7 +316,7 @@ Generated workflows include:
 ```yaml
 validate:
   script:
-    - npx cx-cli --format json modules/*.yaml > validation-results.json
+    - npx cxtms --format json modules/*.yaml > validation-results.json
   artifacts:
     paths:
       - validation-results.json
@@ -331,7 +331,7 @@ validate:
 staged_files=$(git diff --cached --name-only --diff-filter=ACM | grep -E '\.(yaml|yml)$')
 
 if [ -n "$staged_files" ]; then
-  npx cx-cli --format compact $staged_files
+  npx cxtms --format compact $staged_files
   if [ $? -ne 0 ]; then
     echo "Validation failed. Please fix errors before committing."
     exit 1