hyva-exec-shell-cmd
Utility skill to detect Magento development environment and determine command wrapper. This skill should be used by other skills that need to execute shell commands in the Magento environment. It detects Warden, docker-magento, DDEV, and local environments and provides the appropriate command wrapper.
What this skill does
# Execute Shell Commands in Magento Environment This utility skill detects the Magento development environment and provides the appropriate command wrapper for executing shell commands. ## Usage Other skills should reference this skill when they need to execute commands in the Magento environment. The detected wrapper ensures commands run in the correct context (container or local). ## Step 1: Detect Environment **Important:** Execute this script from the Magento project root directory, or provide the path as an argument. Run this detection once at the start of any skill that needs to execute shell commands: ```bash <skill_path>/scripts/detect_env.sh [magento_root_path] ``` Where `<skill_path>` is the directory containing this SKILL.md file (e.g., `.claude/skills/hyva-exec-shell-cmd`). 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 ```bash # 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 ```bash # 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: - `composer` commands (runs on host, not in container) - `git` commands - File operations on the host filesystem (`ls`, `find`, `cp` for files accessible from host) - `warden` CLI commands - `ddev` CLI commands ## Integration Pattern Skills that need to execute commands should: 1. Reference this skill: "Use the `hyva-exec-shell-cmd` skill to determine the command wrapper" 2. Detect environment once using Step 1 3. Store the wrapper pattern for use throughout the skill 4. Apply the wrapper to all container commands per Step 2 <!-- Copyright © Hyvä Themes https://hyva.io. All rights reserved. Licensed under OSL 3.0 -->
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.