govard-magento

name	govard-magento
description	This skill should be used when the user asks to "clear Magento cache", "flush redis cache", "run Magento CLI", "run bin/magento commands", "deploy static content", "setup:di:compile", "reindex catalog", "run indexer commands", "enable/disable modules", "start frontend sync", "run browser-sync", "set up live reload for Hyva/Luma", or "govard frontend". Provides Magento-specific Govard shortcuts and commands. DEPENDENT on govard-toolbox for base commands.
compatibility	claude, codex, opencode, copilot
depends	["govard-toolbox"]
metadata	{"audience":"developers","workflow":"magento"}

Govard Magento Commands

Magento-specific shortcuts and commands for Govard environments.

Related Skills

REQUIRED BACKGROUND: Load govard-toolbox first — this skill only covers Magento-specific shortcuts layered on top of Govard's base environment commands.

This skill covers only container/CLI shortcuts. For module architecture, DI, and security patterns, see magento2-dev-core and magento2-backend-dev; for code quality and performance checks, see magento2-linter, magento2-security-scan, and magento2-performance-audit.

Magento CLI

# Cache management
govard sh -c "bin/magento cache:flush"
govard sh -c "bin/magento cache:clean full_page"

# Specific cache types
govard sh -c "bin/magento cache:enable layout block_html"
govard sh -c "bin/magento cache:disable config"

# Module management
govard sh -c "bin/magento module:enable Vendor_Module"
govard sh -c "bin/magento module:disable Vendor_Module"
govard sh -c "bin/magento module:status"

# Setup commands
govard sh -c "bin/magento setup:di:compile"
govard sh -c "bin/magento setup:static-content:deploy -f"
govard sh -c "bin/magento setup:upgrade --keep-generated"

# Deploy mode
govard sh -c "bin/magento deploy:mode:set developer"
govard sh -c "bin/magento deploy:mode:set production"
govard sh -c "bin/magento deploy:mode:show"

Code Generation

# Generate plugin
govard sh -c "bin/magento generate:plugin Vendor Module"

# Generate observer
govard sh -c "bin/magento generate:observer Vendor Module Event"

# Create admin grid
govard sh -c "bin/magento admin:user:create"

Indexer Commands

# Check status
govard sh -c "bin/magento indexer:status"

# Reindex all
govard sh -c "bin/magento indexer:reindex"

# Single indexer
govard sh -c "bin/magento indexer:reindex catalog_product_price"

# Change mode
govard sh -c "bin/magento indexer:set-mode schedule"
govard sh -c "bin/magento indexer:set-mode realtime"

Cron Commands

# Run cron manually
govard sh -c "bin/magento cron:run"
govard sh -c "bin/magento cron:run --group=default"

# Install crontab
govard sh -c "bin/magento cron:install"

# Remove crontab
govard sh -c "bin/magento cron:remove"

Development Tools

# Template hints (dev only)
govard sh -c "bin/magento dev:template-hints:enable"
govard sh -c "bin/magento dev:template-hints:disable"

# Query logging
govard sh -c "bin/magento dev:query-log:enable"
govard sh -c "bin/magento dev:query-log:disable"

# JS/CSS bundling
govard sh -c "bin/magento dev:js:enable_js_bundling"
govard sh -c "bin/magento dev:css:minify_files"

Frontend Development (BrowserSync / LiveReload)

Requires stack.features.frontend_sync: true in .govard.yml (Magento 2 / Mage-OS only). govard env up never starts this — it's a separate, explicit, on-demand lifecycle:

govard env up                    # app/db/etc. up — no frontend services yet
govard frontend start            # renders + starts BrowserSync/LiveReload + watchers
govard frontend logs -f          # sync/injector container
govard frontend logs watch-<theme> -f
govard frontend stop             # removes only frontend services, keeps their volumes

Prerequisites (Govard never creates or edits these files):

• Hyva: exactly one scripts.browser-sync owner under app/design/frontend/<Vendor>/<Theme>/web/tailwind, with a committed package-lock.json. The theme's own browser-sync.config.js must read GOVARD_FRONTEND_SYNC_TARGET/_PORT from the environment and set changeOrigin: false, cookies.stripDomain: false, open: false, and socket.path: '/browser-sync/socket.io'.
• Luma: root Gruntfile.js, package.json, package-lock.json (copy Magento's .sample files, then npm install). No BrowserSync config needed.
• Hyva and Luma discovery are mutually exclusive project-wide — only one setup may be valid at a time.

Switching the active Hyva theme: move the scripts.browser-sync entry (plus its browser-sync.config.js and package-lock.json) from the old theme's web/tailwind/package.json to the new theme, then run govard frontend start again — it re-discovers whichever theme is now the sole owner.

Symptom	Fix
frontend start reports success but the page redirects to a different host or drops the session	Theme's browser-sync.config.js has changeOrigin/cookies.stripDomain wrong — both must be false
Discovery fails ("no owner found" / conflicting setups)	Confirm exactly one theme owns scripts.browser-sync, and that Hyva and Luma prerequisites aren't both satisfied at once

Database Operations

# Direct MySQL
govard db connect

# Run SQL -- table names here have no prefix; if this project uses one (db.table_prefix in
# app/etc/env.php), prepend it, e.g. `m2_core_config_data` instead of `core_config_data`
govard db query "SELECT * FROM core_config_data WHERE path LIKE '%template%'"

# Import with streaming (fast)
govard db import --stream-db -e staging --drop

# Export from remote
govard db dump -e staging --no-noise --no-pii --local

Configuration

# Show config
govard sh -c "bin/magento config:show system/smtp/host"

# Set config
govard sh -c "bin/magento config:set web/secure/base_url https://local.test/"
govard sh -c "bin/magento config:set design/theme/theme_id 0"

# Import/export config
govard sh -c "bin/magento app:config:dump"
govard sh -c "bin/magento app:config:import"

# Show a config value in every scope it's set (default/website/store) in one
# call -- bin/magento config:show only reads a single scope at a time
govard tool magerun config:store:get web/secure/base_url

Diagnostics

# Environment health check -- missing files/folders, base URL & cookie
# domain settings, required PHP extensions, MySQL InnoDB
govard tool magerun sys:check

# System snapshot (Magento version/edition, app mode, cache backend,
# search engine, module count)
govard tool magerun sys:info

Multi-Website / Multi-Store Setup

Register additional store domains in .govard.yml under store_domains, then let Govard wire up the vhost/DNS side:

domain: "primary.test"
store_domains:
  brand-b.test:
    code: base
    type: website

govard domain add brand-b.test
govard config auto
govard sh -c "bin/magento cache:flush"

Store codes are also selectable via URL path (/fr/, /admin/) without a separate domain — reserve store_domains for genuinely separate hostnames/websites.

Redis Cache

# Flush Redis cache only
govard redis flush

# Redis CLI
govard redis cli

# Check cache info
govard redis info

Varnish (if configured)

# Purge all
govard varnish purge

# Purge by tag
govard sh -c "bin/magento cache:clean cache_tag_frontend"

# Varnish status
govard varnish status

Logging

# View system log
govard sh -c "tail -f var/log/system.log"

# View exception log
govard sh -c "tail -f var/log/exception.log"

# View debug log
govard sh -c "tail -f var/log/debug.log"

# Custom module log
govard sh -c "tail -f var/log/my-module.log"

Common Issues & Solutions

Symptom	Fix
"There are no commands defined" after pulling code	govard sh -c "bin/magento setup:di:compile"
Static assets not updating	govard sh -c "bin/magento setup:static-content:deploy -f" + cache:flush, then hard-refresh the browser
Database connection refused	govard ps (is the DB container up?), govard logs db, then govard down && govard up if needed
Container won't start	govard doctor, then govard logs
Xdebug not connecting	govard debug on, confirm the IDE is listening on port 9003, check the XDEBUG_SESSION cookie matches .govard.yml — see govard-toolbox for the full IDE setup

Template-only changes don't need setup:di:compile — only setup:static-content:deploy. Recompiling DI on every template edit wastes time for no benefit.

Common Workflows

After Pulling Code

govard sh -c "bin/magento setup:upgrade --keep-generated"
govard sh -c "bin/magento setup:static-content:deploy -f"
govard sh -c "bin/magento cache:flush"

After Database Sync

govard config auto   # Rebuild env.php
govard sh -c "bin/magento cache:flush"

Production Deployment Prep

govard sh -c "bin/magento maintenance:enable"
govard sh -c "bin/magento setup:upgrade"
govard sh -c "bin/magento setup:di:compile"
govard sh -c "bin/magento setup:static-content:deploy -f --theme=Vendor/Theme"
govard sh -c "bin/magento cache:flush"
govard sh -c "bin/magento maintenance:disable"