setup

Set Up ado-testcraft Credentials

Instructions

Detect the user's platform, check whether credentials are already set, then output the exact terminal commands they need to paste. Never ask the user to type their PAT into the chat — always use placeholders they replace in the terminal.

Step 1 — Detect operating system

Run $env:OS via PowerShell.

• Returns Windows_NT → Windows. Proceed to the Windows block in Step 3.
• Returns empty or errors → macOS or Linux. Run uname via Bash.
  • Returns Darwin → macOS
  • Returns Linux → Linux

Step 2 — Check current credential state

Read the three variables with the platform-appropriate shell:

Windows (PowerShell):

"ADO_ORG=$($env:ADO_ORG)"; "ADO_PROJECT=$($env:ADO_PROJECT)"; if ($env:ADO_PAT) { "ADO_PAT=[set]" } else { "ADO_PAT=[not set]" }

macOS / Linux (Bash):

echo "ADO_ORG=${ADO_ORG}"; echo "ADO_PROJECT=${ADO_PROJECT}"; [ -n "$ADO_PAT" ] && echo "ADO_PAT=[set]" || echo "ADO_PAT=[not set]"

Show the user a clear credential status summary, masking the PAT:

Current credential state:

• ADO_ORG: [value, or ⚠️ not set]
• ADO_PROJECT: [value, or ⚠️ not set]
• ADO_PAT: [✅ set, or ⚠️ not set]

If all three are already set, say:

✅ All credentials are configured. Test with /ado-testcraft:generate <story-id>. To update any value, paste the replacement commands below into a terminal and restart Claude Code.

Then still show the setup commands in Step 3 for reference and to support credential updates.

Step 3 — Output platform-specific setup commands

Windows

Tell the user to open PowerShell (not Command Prompt) and paste these commands, replacing the placeholder values:

[System.Environment]::SetEnvironmentVariable("ADO_ORG",     "your-org-name",     "User")
[System.Environment]::SetEnvironmentVariable("ADO_PROJECT", "your-project-name", "User")
[System.Environment]::SetEnvironmentVariable("ADO_PAT",     "your-pat-here",     "User")