setup-environment

Automate local dev environment setup by triggering the configuration command to validate Node.js, npm, Git, and Claude Code CLI versions. It enforces blocking checks, verifies repository integrity, and applies environment configurations with an explicit plan before installation.

Phase-driven onboarding setup validates required tooling, config files, and MCP server settings in sequential stages. It prepares a development workstation by checking prerequisites and applying environment configurations non-destructively, stopping immediately if a blocking check fails.

Yes, the environment setup enforces blocking checks for Claude Code CLI and Node.js version requirements. It validates Node.js version 18 or higher, along with npm and Git, to ensure all prerequisites are met before applying repository configurations.

Yes, you can review the configuration plan before the environment setup installs prerequisites. The process presents an explicit, non-destructive plan detailing the changes before executing any installations or applying repository and server configurations.

Your first-time contributor setup stops during repository integrity checks because the configuration process uses blocking checks that halt on failures. It stops to prevent further non-destructive changes if tool versions, prerequisites, or repository states are invalid.