← ClaudeAtlas

add-dev-environment-setuplisted

Use when bash/git/jq/gh CLI are missing or VS Code terminal is not WSL — detects OS, diagnoses gaps, installs missing tools.
brabos-ai/code-addiction · ★ 8 · Code & Development · score 75
Install: claude install-skill brabos-ai/code-addiction
# Dev Environment Setup <!-- uses: - script: status.sh --> ## Overview Detect OS → diagnose silently → confirm → install → configure VS Code. **Never assume what's installed. Never install without confirmation. Never overwrite settings.json.** --- ## When to Use - User asks about environment setup or "how do I run the scripts" - `bash`, `git`, `jq`, or `gh` not found - `status.sh` fails due to missing tool - VS Code terminal opens PowerShell/Git Bash instead of WSL ## When NOT to Use - All tools already installed and verified - User is on Linux with working environment - Container or CI environment (ephemeral; tools provisioned by image/workflow) --- ## ⛔ ABSOLUTE PROHIBITIONS ``` ⛔ NEVER use Bash tool for sudo/apt/dnf/pacman/brew/curl|bash/wsl --install/gh auth login (hangs on password or interactive prompt) ⛔ NEVER overwrite .vscode/settings.json, reinstall WSL when a real distro exists, suggest Git Bash, use `apt-get install gh`, or proceed after user says N ✅ ALWAYS show install commands in code blocks → user runs manually → verify with non-sudo `--version` checks ``` --- ## STEP 1: DETECT OS (MANDATORY FIRST) ```bash uname -s # macOS → Darwin | Linux → Linux $env:OS # Windows PowerShell → Windows_NT ``` ⛔ DO NOT proceed without `TARGET_OS = windows | macos | linux`. --- ## STEP 2: DIAGNOSE (silent — no prompts yet) | Tool | Check | Windows note | |------|-------|-------------| | WSL | `wsl -l -v` | `docker-desktop` only = NOT ready |