Put agents and humans on the
WordPress.org publishing path.
Pressship is one bounded source of truth your agent can fetch — or you can read: inspect the plugin, run the checks, dry-run the route, then confirm before anything uploads or commits.
To prepare a plugin, say this to your agent:
The human page is /ai; plain-text agent instructions are also available at /ai.txt.
npx skills add Automattic/pressship --skill wordpress-plugin-publish -a codexInstalls the dry-run-first publishing skill. No skills runtime? Just hand your agent the prompt above.
wordpress-plugin-publishnpx pressship pack ./my-plugin --dry-runreadme valid · Plugin Check warnings found · zip 3.1 KBnpx pressship publish ./my-plugin --dry-runapproved plugin · SVN release path · confirmation requiredHand the prompt above to any agent and it runs the verified path.
Your agent fetches pressship.org/ai (or installs the skill), then follows the same dry-run-first flow: inspect, validate, package, and ask before any upload or SVN commit.
One runbook, whether you fetch it or read it.
Agents fetch pressship.org/ai; people read the same page. Either way it's one bounded workflow — inspect, validate, package, dry-run — the verified WordPress.org path, with no improvised commands.
One endpoint, two readers
Agents fetch pressship.org/ai and people open the same page — both follow the identical verified WordPress.org publishing flow.
Dry-run before mutation
The endpoint tells agents to inspect, verify, package, and run publish dry runs before upload, reupload, or SVN release.
Works from any agent shell
Codex, Claude Code, Cursor, ChatGPT, OpenCode, and anything that can fetch a URL can learn the path in plain text.
Identify the plugin root
Don't assume the repository root is the plugin root when multiple plugins or build outputs exist.
Check the account and route
$npx pressship whoami$npx pressship info .$npx pressship status .Validate before packaging
$npx pressship verify .Package after validation
$npx pressship pack .Dry-run before any mutation
$npx pressship publish . --dry-run -yAsk before mutating remote state
Pause before any upload, reupload, SVN commit, release tag, or git change.
Human approval required
One predictable path
Run the full flow with publish, or step into any phase explicitly.
- 01
Inspect
Read local plugin metadata and WordPress.org review state at a glance.
npx pressship info ./my-plugin - 02
Studio
Open the local editor, terminal, Playground preview, AI helper, and release sidebar.
npx pressship studio - 03
Package
Validate readme.txt, run Plugin Check, build an installable zip.
npx pressship pack ./my-plugin - 04
Publish
Route to new submission, pending reupload, or SVN release with setup checks.
npx pressship publish ./my-plugin - 05
Demo
Boot the plugin in WordPress Playground using its own requirements.
npx pressship demo ./my-plugin
Designed for plugin authors who ship often
Less yak-shaving around WordPress.org. More time on the plugin itself.
Validates before it uploads
Readme parsing, WordPress.org validator, and Plugin Check all run locally before anything leaves your machine.
Smart publish routing
Detects new submissions, pending reuploads, and approved SVN releases automatically.
SVN setup helper
For get and release flows, Pressship detects missing Subversion and offers the right install path for your OS.
Zero-setup Plugin Check
Managed WordPress and Plugin Check environment. No manual WP-CLI wiring.
Playground demos
Open any local plugin path or hosted slug in WordPress Playground for instant testing.
Agent skill included
Drop-in publishing skill keeps automated workflows dry-run-first and reviewable.
A focused command set
Every command maps to a plugin author task. No nested config, no hidden global state.
npx pressship loginOpen WordPress.org login in a browser and save the session.02npx pressship whoamiShow the active WordPress.org account.03npx pressship infoInspect local plugin metadata or hosted plugin info.04npx pressship lsList profile plugins and saved-account SVN committer plugins.05npx pressship getCheckout or update SVN, with Subversion setup help.06npx pressship studioOpen the local editor, terminal, and Playground preview.07npx pressship statusRead submission state from the developer dashboard.08npx pressship packValidate, run Plugin Check, and write an installable zip.09npx pressship publishRoute to submit or release based on current state.10npx pressship submitUpload a zip to WordPress.org review or reupload.11npx pressship releasePush an approved release through SVN trunk and tags.12npx pressship demoOpen the plugin in WordPress Playground.13npx pressship versionBump plugin and readme version together.A plugin workspace that keeps the boring parts close.
Run npx pressship studio and work from a VS Code-like surface where files, Playground, Plugin Check, AI review, package sizing, and SVN release management all point at the same local plugin.
Check findings become editor work
Plugin Check output is tied back to the file tree, line markers, and terminal command that produced it.
AI changes stay reviewable
The helper can fix, refactor, or update readme text, but file changes still move through explicit accept and reject controls.
Release decisions are visible
Submit, reupload, release, SVN tags, ignored files, package size, and confirmation steps are kept in the right pane.
Fix warnings where they happen, with the editor, terminal, and AI helper in one frame.
Plugin Check findings stay pinned to file and line context. The helper can propose patches, but accepting or rejecting changes stays explicit.
Ready to ship your next plugin?
Set up Pressship in under a minute and stop fighting the WordPress.org publishing dance.