xray-clilisted

# Xray CLI - Test Management ## Modality check (critical) This skill owns `[TMS_TOOL]` **only in Modality jira-xray** (Jira Cloud + Xray plugin installed). Before invoking any command from this skill: 1. Confirm the project is in Modality jira-xray. Resolution logic lives in `test-documentation/SKILL.md` §Phase 0. 2. If the project is in Modality jira-native (no Xray plugin) -> **do not use this skill**. Instead, load `/acli` — TMS operations map to native Jira issues (see `test-documentation/references/jira-setup.md`). Agents arriving here from a `[TMS_TOOL] ...` pseudocode block without having resolved modality first should pause and consult the modality resolver before proceeding. ## Quick start ```bash # Check authentication status bun xray auth status # Login with credentials bun xray auth login --client-id ABC123 --client-secret xyz789 # List tests in a project bun xray test list --project DEMO # Create a test execution bun xray exec create --project DEMO --summary "Sprint 1 Tests" # Import JUnit results bun xray import junit --file results.xml --project DEMO ``` ## Issue references: Jira keys vs numeric IDs Every flag that takes an issue reference (`--execution`, `--plan`, `--set`, `--tests`, plus the positional argument of `exec get` / `set get`) accepts **both forms** interchangeably: - **Jira key**: `{{PROJECT_KEY}}-194` — resolved via Jira REST in-process. Requires Jira credentials configured (`auth login --jira-url --jira-email --jira-token` or the `JIRA_