wp-editslisted
Install: claude install-skill roama-studio/skills
# Edits to an existing WordPress site (Playground copy)
First run: a classic-theme site + an Elementor probe, 2026-10-23. The tool is
`qa-kit wp-site` (on PATH with this plugin; its README: `tools/qa-kit/README.md`).
Sister skills: `wp-deploy` (how a site gets copied from / to hosting over SSH),
`wp-classic-theme` (themes you build), `wp-theme-qa` (checking a theme).
## 0. Rules
- **The live site is never touched while editing.** Everything happens in a copy
in the order's workspace (git-ignored). Reading the live site over SSH (a
`mysqldump`, `tar` of the files) is allowed only with the site owner's
permission and is read-only.
- **No passwords.** wp-admin of the copy opens through Playground's auto-login
link (`site.json` -> `admin`); nobody types the client's password anywhere.
- **Every edit is a command.** Write each change as the WP-CLI command (or the
changed file) into the order's `EDITS.md` / edit script in the order you ran
it: after the client approves, the same commands are applied to the live site,
so new leads and orders on the live site are never overwritten.
- **Two copies:** `original` (never edited: the baseline for QA) and `edited`.
Import both from the same copy, on different ports.
- **No window on the user's desktop** (Playground starts can open terminal
windows over the user's work). Every process a tool starts is
invisible: always go through `qa-kit wp-site` (never `npx @wp-playground/cli`
by hand: npx runs a `cmd.exe` shim). I