@local-labs-jpollock/local-cli 0.0.3 → 0.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@local-labs-jpollock/local-cli",
-  "version": "0.0.3",
+  "version": "0.0.5",
   "description": "Command-line interface for Local WordPress development",
   "main": "lib/index.js",
   "bin": {

package/skill/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: lwp
-description: Manage Local WordPress development sites using the lwp CLI. Use when the user asks about WordPress sites, Local development, starting/stopping sites, running WP-CLI commands, or managing local WordPress environments.
+description: Manage Local WordPress development sites using the lwp CLI. Use when the user asks about WordPress sites, Local development, starting/stopping sites, running WP-CLI commands, or managing local WordPress environments. Local is a free development tool built and supported by WP Engine.
 allowed-tools: Bash(lwp *)
 ---
 
 # Local CLI (lwp)
 
-The `lwp` command manages WordPress sites in [Local](https://localwp.com), a local WordPress development environment.
+The `lwp` command manages WordPress sites in [Local](https://localwp.com), a local WordPress development environment built and supported by WP Engine.
 
 ## Prerequisites
 
@@ -45,6 +45,21 @@ lwp wp <site> cache flush
 lwp wp <site> search-replace 'old' 'new' --dry-run
 ```
 
+**Plugin-provided CLI commands** (e.g., `wp migrate`):
+
+By default, plugins are skipped for safety. Use `--with-plugins` to load them.
+
+**Important:** Options must come BEFORE the site name:
+
+```bash
+# Correct - option before site:
+lwp wp --with-plugins <site> migrate push <target>
+lwp wp --with-plugins <site> migrate pull <source>
+
+# Wrong - option will be passed to WP-CLI:
+lwp wp <site> --with-plugins migrate push  # DON'T DO THIS
+```
+
 ### Database Operations
 
 ```bash
@@ -129,6 +144,29 @@ lwp sites list --json | jq '.[].name'
 | "Timed out waiting for Local" | Start the Local application |
 | "Site not found" | Check site name with `lwp sites list` |
 
+## Destructive Commands - Confirm First
+
+**Always confirm with the user before running these commands:**
+
+| Command | Risk |
+|---------|------|
+| `lwp sites delete <site>` | Permanently deletes site and files |
+| `lwp db import <site> <file>` | Overwrites entire database |
+| `lwp wpe push <site>` | Pushes to production WP Engine site |
+| `lwp backups restore <site>` | Overwrites site from backup |
+| `lwp wp <site> db reset` | Drops all database tables |
+| `lwp wp <site> search-replace` | Modifies database content |
+
+**Safe practices:**
+
+1. **Export first** - Always run `lwp db export <site>` before destructive operations
+2. **Dry run** - Use `--dry-run` when available to preview changes:
+   ```bash
+   lwp wp <site> search-replace 'old' 'new' --dry-run
+   ```
+3. **Confirm intent** - Ask "Are you sure you want to delete/overwrite X?" before proceeding
+4. **Never auto-confirm** - Do not add `-y` or `--yes` flags without explicit user approval
+
 ## Tips
 
 1. Always check site status before running WP-CLI commands