check-tools

# Check Tools - Development Environment Validator Reports which development tools are installed and at what version, grouped by ecosystem. Default behavior reports every tool without failing validation — suited to diverse PaaS/container environments where only a subset of ecosystems is expected to be present. ## When to use - Verifying a container or environment has the tools a task needs - Troubleshooting a build failure that might be a missing dependency - Documenting system requirements - Onboarding: confirming a dev environment is ready ## Running it ```bash # Fast check with exit code (0 = all required core tools present) bash assets/check-tools.sh # Development tools only bash assets/environment-diagnostic.sh tools # System info: hardware, mounts, processes bash assets/environment-diagnostic.sh system # Complete diagnostic (tools + system + package inventories), written to a file bash assets/environment-diagnostic.sh full /path/to/report.txt ``` `check-tools.sh` exits non-zero only when a **required** core tool (python3, pip, node, npm, java, gcc, git, curl, awk, grep, gzip, tar, make, sed) is missing. Every other tool is reported (✅ found / ⚠️ optional and missing) but does not fail the run. ## Required vs. optional, by ecosystem | Ecosystem | Required | Optional | |-----------|----------|----------| | Python | python3, pip | python, uv, poetry, black, mypy, pytest, ruff | | Node.js | node, npm | nvm, yarn, pnpm, eslint, prettier, chromedriver | | Java ...