wordpress-plugin-publish

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 or the WP-CLI package (wp ship).

Install Surfaces

Use the install surface the user asks for:

npx pressship verify .
wp package install f/pressship
wp ship verify .
npm install -g pressship
pressship verify .

For agent skill installation:

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

• Never publish, submit, reupload, or release without first running a dry run, unless the user explicitly says to skip it.
• 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

From the plugin directory:

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

Start a local WordPress Playground with the plugin mounted:

npx pressship demo .

Useful options: