Prerequisites Check

Validate that the local environment has the CLI tools and auth sessions needed to run Git-Ape skills. Print platform-specific install commands and PATH-repair guidance for anything missing or version-stale.

Quick Reference

When to Use

• Before first-time onboarding (/git-ape-onboarding)
• When any Git-Ape skill fails with command not found
• When the user reports a missing binary in their prompt (e.g., az: command not found)
• After switching machines, shells, or dev containers
• When the user asks "what do I need to install?"

Rules

1. Run read-only — never brew install, apt-get install, or any state-changing command. Print the commands; the user runs them.
2. Trust user reports — if the user reports a tool missing, treat it as ⚠️ even when this terminal can find it (different shell, PATH, container, or machine).
3. Stop at first blocking failure — do not continue to auth checks while any tool is ❌.
4. Do not chain into other skills — never auto-invoke git-ape-onboarding; tell the user to run it after READY.

Steps

Status Table

scripts/check-tools.sh emits TSV rows of tool<TAB>status<TAB>found<TAB>minimum. Render them as:

Status mapping:

• OK → ✅
• OUTDATED or MISSING → ❌
• Reported missing in Step 2 but OK in this terminal → ⚠️ with note reported missing by user

Auth Checks

macOS / Linux (bash):

az account show --query "{name:name,id:id,tenantId:tenantId}" -o table 2>/dev/null \
  || echo "❌ Not logged in to Azure. Run: az login"

gh auth status 2>/dev/null \
  || echo "❌ Not logged in to GitHub. Run: gh auth login"

Windows (PowerShell 7+):

az account show --query "{name:name,id:id,tenantId:tenantId}" -o table 2>$null
if (-not $?) { Write-Output "❌ Not logged in to Azure. Run: az login" }

gh auth status 2>$null
if (-not $?) { Write-Output "❌ Not logged in to GitHub. Run: gh auth login" }

Outputs

A single chat message containing:

1. Status table from Step 4.
2. Install / PATH repair commands for ❌ and ⚠️ entries — pulled from references/install-commands.md, scoped to the detected platform.
3. Auth status (Azure subscription + GitHub user) from Step 6, only when all tools ✅.
4. Final verdict — exactly one of:
   • ✅ READY — all tools installed, versions OK, auth sessions active. Render the handoff chip from ## Next so the user can click into onboarding.
   • ⚠️ TOOLS MISSING — list what to install. Do not continue.
   • ⚠️ REPORTED MISSING — this terminal finds the tool but the user reported it missing. Print install / PATH repair + verification block.
   • ⚠️ AUTH MISSING — tools OK but az login and/or gh auth login required.

Error Handling

Constraints

Always:

• Print install commands; let the user run them
• Detect platform before printing recipes
• Honor user-reported missing tools even when this terminal finds them
• Stop at the first blocking failure
• Verify with command -v <tool> + <tool> --version after suggested fixes

Never:

• Run brew install, apt-get install, winget install, or any state-changing command
• Require git-bash on Windows — use the PowerShell script (scripts/check-tools.ps1) instead
• Auto-invoke git-ape-onboarding after a READY verdict
• Silently drop a reported-missing tool because this terminal finds it
• Continue to auth checks while any tool is ❌
• Recommend sudo on macOS (Homebrew handles non-root install)

Next

After a ✅ READY verdict, render this line verbatim so the chat surface turns it into a clickable handoff:

Next: @Git-Ape Onboarding — or run /git-ape-onboarding to start setup.

VS Code Copilot Chat renders @AgentName mentions and /skill-name slash commands as clickable chips — the user clicks once to dispatch. Do not auto-invoke (Rule 4).

For deployment-time validation of an Azure project, use azure-validate instead.