@local-labs-jpollock/local-cli 0.0.2 → 0.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@local-labs-jpollock/local-cli",
3
- "version": "0.0.2",
3
+ "version": "0.0.4",
4
4
  "description": "Command-line interface for Local WordPress development",
5
5
  "main": "lib/index.js",
6
6
  "bin": {
package/skill/SKILL.md CHANGED
@@ -1,12 +1,12 @@
1
1
  ---
2
2
  name: lwp
3
- 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.
3
+ 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.
4
4
  allowed-tools: Bash(lwp *)
5
5
  ---
6
6
 
7
7
  # Local CLI (lwp)
8
8
 
9
- The `lwp` command manages WordPress sites in [Local](https://localwp.com), a local WordPress development environment.
9
+ The `lwp` command manages WordPress sites in [Local](https://localwp.com), a local WordPress development environment built and supported by WP Engine.
10
10
 
11
11
  ## Prerequisites
12
12
 
@@ -45,6 +45,15 @@ lwp wp <site> cache flush
45
45
  lwp wp <site> search-replace 'old' 'new' --dry-run
46
46
  ```
47
47
 
48
+ **Plugin-provided CLI commands** (e.g., `wp migrate`):
49
+
50
+ By default, plugins are skipped for safety. Use `--with-plugins` to load them:
51
+
52
+ ```bash
53
+ lwp wp <site> --with-plugins migrate push <target>
54
+ lwp wp <site> --with-plugins migrate pull <source>
55
+ ```
56
+
48
57
  ### Database Operations
49
58
 
50
59
  ```bash
@@ -129,6 +138,29 @@ lwp sites list --json | jq '.[].name'
129
138
  | "Timed out waiting for Local" | Start the Local application |
130
139
  | "Site not found" | Check site name with `lwp sites list` |
131
140
 
141
+ ## Destructive Commands - Confirm First
142
+
143
+ **Always confirm with the user before running these commands:**
144
+
145
+ | Command | Risk |
146
+ |---------|------|
147
+ | `lwp sites delete <site>` | Permanently deletes site and files |
148
+ | `lwp db import <site> <file>` | Overwrites entire database |
149
+ | `lwp wpe push <site>` | Pushes to production WP Engine site |
150
+ | `lwp backups restore <site>` | Overwrites site from backup |
151
+ | `lwp wp <site> db reset` | Drops all database tables |
152
+ | `lwp wp <site> search-replace` | Modifies database content |
153
+
154
+ **Safe practices:**
155
+
156
+ 1. **Export first** - Always run `lwp db export <site>` before destructive operations
157
+ 2. **Dry run** - Use `--dry-run` when available to preview changes:
158
+ ```bash
159
+ lwp wp <site> search-replace 'old' 'new' --dry-run
160
+ ```
161
+ 3. **Confirm intent** - Ask "Are you sure you want to delete/overwrite X?" before proceeding
162
+ 4. **Never auto-confirm** - Do not add `-y` or `--yes` flags without explicit user approval
163
+
132
164
  ## Tips
133
165
 
134
166
  1. Always check site status before running WP-CLI commands