pressship 0.1.11 → 0.1.12

package/.claude/skills/wordpress-plugin-publish/SKILL.md

@@ -1,11 +1,30 @@
 ---
 name: wordpress-plugin-publish
-description: Use this skill when publishing, submitting, reuploading, packaging, checking, or releasing WordPress.org plugins with Pressship. It covers safe Pressship workflows for local plugin directories, pending WordPress.org submissions, approved plugin releases, Plugin Check review, package exclusions, WordPress Playground demos, and authentication.
+description: Use this skill when publishing, submitting, reuploading, verifying, packaging, checking, demoing, or releasing WordPress.org plugins with Pressship. It covers safe Pressship workflows for local plugin directories, WordPress.org SVN checkouts, pending submissions, approved releases, Plugin Check review, package exclusions, WordPress Playground demos, WP-CLI usage, and authentication.
 ---
 
 # WordPress Plugin Publish
 
-Use Pressship for WordPress.org plugin submission and release work. Prefer `npx pressship` unless the user explicitly wants the local checkout version.
+Use Pressship for WordPress.org plugin submission and release work. Prefer `npx pressship` unless the user explicitly wants the local checkout version or the WP-CLI package (`wp ship`).
+
+## Install Surfaces
+
+Use the install surface the user asks for:
+
+```bash
+npx pressship verify .
+wp package install f/pressship
+wp ship verify .
+npm install -g pressship
+pressship verify .
+```
+
+For agent skill installation:
+
+```bash
+npx skills add f/pressship --skill wordpress-plugin-publish -a codex
+npx skills add f/pressship --skill wordpress-plugin-publish -a claude-code
+```
 
 ## Safety Rules
 
@@ -13,8 +32,10 @@ Use Pressship for WordPress.org plugin submission and release work. Prefer `npx
 - Do not push git commits or tags unless the user explicitly asks.
 - Report Plugin Check findings clearly. Do not hide them just because Pressship can continue.
 - Use repeatable excludes for large or source-only files. Prefer `.pressshipignore` when the project already has one.
+- Use `--no-verify` only when the user explicitly asks to bypass readme validation and Plugin Check.
 - If Pressship prompts interactively, answer only with user-approved or obvious plugin metadata.
 - If authentication fails, run `npx pressship login` and let the user complete WordPress.org login.
+- For approved-plugin SVN releases, expect Pressship to verify before SVN changes, reject already-published versions, and ask for a generated WordPress.org SVN password when needed.
 
 ## Orientation
 
@@ -22,11 +43,14 @@ From the plugin directory:
 
 ```bash
 npx pressship whoami
+npx pressship verify .
 npx pressship status .
 npx pressship info .
+npx pressship info --remote
 ```
 
 Use `status` to determine whether `publish` will target a pending submission reupload or an approved SVN release.
+Use `verify` when you need readme validation and Plugin Check without creating a zip.
 
 ## Local Playground Test
 
@@ -45,9 +69,15 @@ npx pressship demo . --reset
 npx pressship demo . --skip-browser
 ```
 
-## Package Check
+## Verify And Package
 
-Create and validate a WordPress-installable zip without uploading:
+Run the publishing checks without creating a zip:
+
+```bash
+npx pressship verify .
+```
+
+Create a validated WordPress-installable zip without uploading:
 
 ```bash
 npx pressship pack .
@@ -59,7 +89,14 @@ For projects with bulky assets or source-only files, pass explicit ignores:
 npx pressship pack . --ignore "assets/**" --ignore "src/**" --ignore "node_modules/**"
 ```
 
-Inspect package file count and included paths. Make sure the ZIP contains runtime PHP, built assets, `readme.txt`, and any required examples or static assets.
+`pack`, `publish`, `submit`, and SVN `release` verify by default. If the user explicitly chooses to bypass checks, use the unified flag:
+
+```bash
+npx pressship pack . --no-verify
+npx pressship publish . --no-verify
+```
+
+Inspect package file count and included paths. Make sure the ZIP contains runtime PHP, built assets, `readme.txt`, and any required examples or static assets. Confirm `.pressship-svn` is never included.
 
 ## Submit Or Reupload Pending Review
 
@@ -111,6 +148,18 @@ npx pressship status .
 
 Use this only when the plugin is already approved and the user wants a WordPress.org release.
 
+For an existing WordPress.org plugin, the normal SVN-based edit flow is:
+
+```bash
+npx pressship get my-plugin ./my-plugin
+cd ./my-plugin
+npx pressship version patch
+npx pressship publish --release --dry-run -y
+npx pressship publish --release -y
+```
+
+Pressship treats the SVN checkout root as the project root and edits `trunk/`. It should stop with "No version change detected" if the target tag already exists.
+
 Dry run first:
 
 ```bash
@@ -130,6 +179,8 @@ npx pressship release . --slug my-plugin --username WpOrgUser --dry-run
 npx pressship release . --slug my-plugin --username WpOrgUser -y
 ```
 
+If `svn` is missing, let Pressship detect the OS and offer installation, or pass `--no-install-svn` only when the user wants manual setup. If the SVN password is missing, Pressship points to the user's WordPress.org SVN password page and saves the generated password locally after they provide it.
+
 ## Version Bumps
 
 Only run version bumps when the user asks:
@@ -147,7 +198,9 @@ After a version bump, review changed plugin headers, `readme.txt` stable tag, an
 Always include:
 
 - Whether a dry run was run.
+- Whether `verify` ran and whether validation was bypassed.
 - Package size and notable included/excluded files.
 - Plugin Check result summary.
 - Upload/release status and slug.
+- SVN checkout/tag status for approved releases.
 - Whether git was left untouched or changed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pressship",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "description": "Submit and release WordPress.org plugins from the command line.",
   "homepage": "https://pressship.org",
   "bin": {
@@ -21,9 +21,10 @@
     "build": "tsc -p tsconfig.json",
     "browsers:install": "playwright install chromium",
     "dev": "tsx src/cli.ts",
-    "docs:build": "npm run build --prefix website",
-    "docs:dev": "npm run start --prefix website",
-    "docs:serve": "npm run serve --prefix website",
+    "check-docs": "node -e \"const fs=require('fs');if(!fs.existsSync('website/node_modules')){console.error('\\x1b[31mError: Please run \\x1b[33mnpm install --prefix website\\x1b[31m first.\\x1b[0m');process.exit(1)}\"",
+    "docs:build": "npm run check-docs && npm run build --prefix website",
+    "docs:dev": "npm run check-docs && npm run start --prefix website",
+    "docs:serve": "npm run check-docs && npm run serve --prefix website",
     "test": "vitest run",
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },