Enonic CLI & Local Dev Environment Helper

Procedures

Step 1: Detect Workspace Context

1. Execute node scripts/find-enonic-targets.mjs from the skill root to scan the current workspace for Enonic project markers (.enonic, build.gradle with com.enonic.xp plugin, gradle.properties with xpVersion).
2. If markers are found, note the project name, linked sandbox, and XP version from the output. Use these values as defaults for subsequent commands.
3. If no markers are found, treat the request as a greenfield setup and proceed to sandbox creation or project scaffolding as appropriate.

Step 2: Ensure CLI is Available

1. Verify the Enonic CLI is installed by running enonic --version.
2. If the command fails, read references/cli-reference.md for installation instructions and guide through the appropriate method for the detected OS:
   • npm (any OS): npm install -g @enonic/cli
   • macOS: brew tap enonic/cli && brew install --no-quarantine enonic
   • Linux: wget -qO- https://repo.enonic.com/public/com/enonic/cli/installer/cli-linux/1.0.0/cli-linux-1.0.0.sh | sh
   • Windows: scoop bucket add enonic https://github.com/enonic/cli-scoop.git && scoop install enonic
3. After installation, verify with enonic --version.