wp-wpcli-and-ops/SKILL.md

---

name: wp-wpcli-and-ops description: "Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml." compatibility: "Targets WordPress 7.0+ (PHP 7.4.0+). Requires WP-CLI in the execution environment."

---

BB Skills installed path and bounded native evidence (2026-10-04)

Set BB_SKILL_DIR to the absolute directory containing this installed SKILL.md and supply the actual WordPress root via --path=/absolute/root; on PowerShell use $env:BB_SKILL_DIR in the command. The helper and every reference are bundled. Review WP-CLI on PATH and the target installation before running: commands bootstrap WordPress and may load plugin code. Use an authorized disposable or staging target and an external time limit; the helper has no built-in subprocess timeout.

BB Skills executed native diagnostic helpers against a fresh WordPress 7.1.2 / WP-CLI 2.12.0 installation with synthetic options and file markers. Results, environment versions, image identities and exact source hashes are in examples/native-cli-evidence.json. The example runner and setup are included; its WP-CLI PHAR and Node executable must be obtained and verified separately. This checks selected helper behavior, not an AI client's execution of the complete skill. runtime_tested remains false for that full-skill claim. No performance benchmark, real migration, persistent cache, multisite operation or production site was tested.

Read JSON readiness fields rather than trusting process exit 0: a missing WP-CLI or invalid target still produces a report. An unavailable doctor/profile subcommand is not a clean diagnostic result. File-presence signals do not establish plugin activation, a functioning cache or a speedup. Use the original sources and authoring notices retained under upstream-original and source-context to distinguish upstream instructions from BB Skills additions. All additions follow GPL-2.0-or-later.

The native operations inspector identified this single-site install, core version and configured URLs. No search-replace, import/export restore, cron execution, cache flush, plugin update, user management or network-wide write was executed. Plan, back up and verify those operations separately before using their documented commands on a real installation. The upstream helper source is unchanged.

WP-CLI and Ops

When to use

Use this skill when the task involves WordPress operational work via WP-CLI, including:

• 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)

Inputs required

• Where WP-CLI will run (local dev, staging, production) and whether it’s safe to run.
• How to target the correct site root:
• --path=<wordpress-root> and (multisite) --url=<site-url>
• Whether this is multisite and whether commands should run network-wide.
• Any constraints (no downtime, no DB writes, maintenance window).

Procedure

0) Guardrails: confirm environment and blast radius

WP-CLI commands can be destructive. Before running anything that writes:

1. Confirm environment (dev/staging/prod).
2. Confirm targeting (path/url) so you don’t hit the wrong site.
3. Make a backup when performing risky operations.

Read: - references/safety.md

1) Inspect WP-CLI and site targeting (deterministic)

Run the inspector:

• node "$BB_SKILL_DIR/scripts/wpcli_inspect.mjs" --path=<path> [--url=<url>]

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.

2) Choose the right workflow

A) Safe URL/domain migration (search-replace)

Follow a safe sequence:

1. wp db export (backup)
2. wp search-replace --dry-run (review impact)
3. Run the real replace with appropriate flags
4. Flush caches/rewrite if needed

Read: - references/search-replace.md

B) Plugin/theme operations

Use wp plugin * / wp theme * and confirm you’re acting on the intended site (and network) first.

Read: - references/packages-and-updates.md

C) Cron and queues

Inspect cron state and run individual events for debugging rather than “run everything blindly”.

Read: - references/cron-and-cache.md

D) Multisite operations

Multisite changes can affect many sites. Always decide whether you’re operating:

• on a single site (--url=), or
• network-wide (--network / iterating sites)

Read: - references/multisite.md

3) Automation patterns (scripts + wp-cli.yml)

For repeatable ops, prefer:

• wp-cli.yml for defaults (path/url, PHP memory limits)
• shell scripts that log commands and stop on error
• CI jobs that run read-only checks by default

Read: - references/automation.md

Verification

• Re-run wpcli_inspect after changes that could affect targeting or config.
• Confirm intended side effects:
• correct URLs updated
• plugins/themes in expected state
• cron/caches flushed where needed
• If there’s a health check endpoint or smoke test suite, run it after ops changes.

Failure modes / debugging

• “Error: This does not seem to be a WordPress installation.”
• wrong --path, wrong container, or missing wp-config.php
• Multisite commands affecting the wrong site
• missing --url or wrong URL
• Search-replace causes unexpected serialization issues
• wrong flags or changing serialized data unsafely

See: - references/debugging.md

Escalation

• If you cannot confirm environment safety, do not run write operations.
• If the repo uses containerized tooling (Docker/wp-env) but you can’t access it, ask for the intended command runner or CI job.