SKILL.md
$27
The optional magento_root_path argument specifies the Magento installation directory. If omitted, the script uses the current working directory.
Output: warden, docker-magento, ddev, or local
Step 2: Apply Command Wrapper
Based on detected environment, wrap commands as follows:
Environment
Command Wrapper
Description
Warden
warden env exec -T php-fpm bash -c "<command>"
Docker environment managed by Warden
docker-magento
bin/clinotty bash -c "<command>"
Mark Shust's docker-magento setup
DDEV
ddev exec <command>
DDEV containerized environment
Local
Run <command> directly
Native environment without containers
Examples
Single command
# Warden
warden env exec -T php-fpm bash -c "bin/magento cache:clean"
# docker-magento
bin/clinotty bash -c "bin/magento cache:clean"
# DDEV
ddev exec bin/magento cache:clean
# Local
bin/magento cache:clean
Command with directory change
# Warden
warden env exec -T php-fpm bash -c "cd vendor/hyva-themes/magento2-default-theme/web/tailwind && npm run build"
# docker-magento
bin/clinotty bash -c "cd vendor/hyva-themes/magento2-default-theme/web/tailwind && npm run build"
# DDEV
ddev exec bash -c "vendor/hyva-themes/magento2-default-theme/web/tailwind && npm run build"
# Local
cd vendor/hyva-themes/magento2-default-theme/web/tailwind && npm run build
Commands That Do NOT Require Wrapping
Some commands run on the host system and should NOT be wrapped:
composercommands (runs on host, not in container)
gitcommands
- File operations on the host filesystem (
ls,find,cpfor files accessible from host)
wardenCLI commands
ddevCLI commands
Integration Pattern
Skills that need to execute commands should:
- Reference this skill: "Use the
hyva-exec-shell-cmdskill to determine the command wrapper"
- Detect environment once using Step 1
- Store the wrapper pattern for use throughout the skill
- Apply the wrapper to all container commands per Step 2