wp-wpcli-and-ops

Use this skill when the task involves WordPress operational work via WP-CLI, including: WP-CLI commands can be destructive. Before running anything that writes: Read: Run the inspector: If WP-CLI isn’t available, fall back to installing it via the project’s documented tooling (Composer, container, or system package), or ask for the expected execution environment. Follow a safe sequence: Read: Use wp plugin * / wp theme * and confirm you’re acting on the intended site (and network) first. Read: Inspect cron state and run individual events for debugging rather than “run everything blindly”. Read: Multisite changes can affect many sites. Always decide whether you’re operating: Read: For repeatable ops, prefer: Read: See: - wp search-replace (URL changes, domain migrations, protocol switch) - DB export/import, resets, and inspections ( wp db * ) - plugin/theme install/activate/update, language packs - cron event listing/running - cache/rewrite flushing - multisite operations ( wp site * , --url , --network ) - building repeatable scripts ( wp-cli.yml , shell scripts, CI jobs) - Where WP-CLI will run (local dev, staging, production) and whether it’s safe to run. - How to target the correct site root: - --path= and (multisite) --url= - Whether this is multisite and whether commands should run network-wide. - Any constraints (no downtime, no DB writes, maintenance window).