Setup Scripts

Procedure

1. Create ~/.claude/scripts/ if it does not exist
2. For each script in the inventory above, check if it exists and is executable
3. If missing, read the current version from this skill's embedded templates below and write it
4. If it exists, check its version comment against the template — offer to update if outdated
5. Run chmod +x on all scripts
6. Smoke test each script (run with --help or a quick org name) and report pass/fail

Templates

The templates for each script are maintained in the script files themselves. This skill should read the existing scripts at ~/.claude/scripts/*.sh to verify they exist.

If any are missing, regenerate them by:

1. Reading ~/.claude/scripts/_lib.sh for the shared library pattern
2. Following the same pattern (source _lib.sh, use get_gh_org, parse_repo_names)
3. Outputting JSON to stdout
4. Using set -euo pipefail and bash 3.2 compatibility (no mapfile, no associative arrays)

Bash 3.2 compatibility rules

macOS ships bash 3.2. All scripts MUST:

• Not use mapfile — use while IFS= read -r loops instead
• Not use associative arrays (declare -A) — use parallel indexed arrays
• Not use |& — use 2>&1 |
• Not use [[ =~ ]] with literal ) in patterns — use sed for extraction
• Use $(( )) for arithmetic, not let
• Process substitution < <() works on macOS bash 3.2 but test if unsure

Validation

After generating, run each script and verify:

• Exit code 0
• Output is valid JSON (pipe through jq .)
• No bash syntax errors

Report results as a table:

Auto-Exit When Standalone

IMPORTANT: If this command is being run as a standalone request, automatically exit after completing all phases successfully.