hyva-exec-shell-cmd

Detects Magento dev environment and returns appropriate shell command wrapper.

78|16|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/hyva-themes/hyva-ai-tools --skill hyva-exec-shell-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyva-exec-shell-cmd
Source: https://github.com/hyva-themes/hyva-ai-tools/tree/main/skills/hyva-exec-shell-cmd
Command: npx skills add https://github.com/hyva-themes/hyva-ai-tools --skill hyva-exec-shell-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill detects the Magento development environment and provides the appropriate command wrapper so shell commands execute in the correct container or host context.

Core Features & Use Cases

  • Environment detection: identifies Warden, docker-magento, DDEV, or local.
  • Command wrapping: supplies a ready-to-use wrapper that executes commands in the detected environment.
  • Use case: When automating Magento tasks across multiple environments, such as running bin/magento in a container from scripts.

Quick Start

Run the detect_env.sh script located in the skill directory to determine the environment: <skill_path>/scripts/detect_env.sh [magento_root_path]

Frequently Asked Questions about hyva-exec-shell-cmd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect my Magento development environment for running shell commands?

Magento environment detection identifies Warden, docker-magento, DDEV, or local setups by checking .env files, bin/clinotty, and DDEV config, returning the correct command wrapper for executing shell commands in the proper context.

What's the best way to run bin/magento commands across different Docker environments?

Running bin/magento commands across Docker environments requires a wrapper that detects Warden, docker-magento, or DDEV configurations and supplies a portable command string ensuring execution occurs inside the correct container context.

Does this environment detection work with both Warden and DDEV for Magento?

Environment detection works with Warden, docker-magento, DDEV, and local Magento setups, applying specific heuristics like .env files, bin/clinotty presence, and DDEV config to identify the active environment and provide the correct wrapper.

How do I execute Magento shell commands from scripts without manually specifying the container?

Executing Magento shell commands from scripts without manual container specification involves running a detection script that analyzes environment markers and returns a ready-to-use wrapper command for automated task execution.

Why should I use an environment wrapper instead of calling bin/magento directly?

Using an environment wrapper instead of calling bin/magento directly ensures commands execute in the correct container context across Warden, DDEV, or local environments, preventing errors when automating Magento tasks across multiple development setups.