close
Skip to main content
Install the agent skill
$npx skills add Automattic/pressship --skill wordpress-plugin-publish -a codex

WordPress.org plugin publishing,
from the terminal.

Pressship validates, packages, submits, releases, inspects, and demos WordPress.org plugins — with review, SVN, and local setup steps kept explicit while the chores stay quiet.

Get startedGitHub
$npx pressship publish ./my-plugin
Terminal
$npx pressship info ./my-plugin
Plugin     my-plugin v1.0.3
Requires   WordPress 6.4 · PHP 7.4
Route      approved · SVN release
$npx pressship pack ./my-plugin
readme.txt  valid
Plugin Check 5 warnings
Archive    my-plugin.zip · 3.1 KB
$npx pressship publish ./my-plugin --dry-run
Checks    readme · Plugin Check · SVN
Plan      commit trunk + tag 1.0.3
dry-run   no upload · add --yes when ready
Terminal

Run the publishing path from the terminal first. Open Studio when you want the workspace.

Pressship starts as commands: inspect the plugin, package it, dry-run the WordPress.org route, then choose when to upload or commit.

×Built on WordPress.org review, Plugin Check, SVN, Subversion setup helpers, and WordPress Playground.
Workflow

One predictable path

Run the full flow with publish, or step into any phase explicitly.

  1. 01

    Inspect

    Read local plugin metadata and WordPress.org review state at a glance.

    npx pressship info ./my-plugin
  2. 02

    Studio

    Open the local editor, terminal, Playground preview, AI helper, and release sidebar.

    npx pressship studio
  3. 03

    Package

    Validate readme.txt, run Plugin Check, build an installable zip.

    npx pressship pack ./my-plugin
  4. 04

    Publish

    Route to new submission, pending reupload, or SVN release with setup checks.

    npx pressship publish ./my-plugin
  5. 05

    Demo

    Boot the plugin in WordPress Playground using its own requirements.

    npx pressship demo ./my-plugin
What you get

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.

Commands

A focused command set

Every command maps to a plugin author task. No nested config, no hidden global state.

01npx 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.
Studio

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.

Read the Studio guide
Pressship Studio
Pressship Studio workspace showing a plugin file, Plugin Check warnings, terminal output, and the AI helper pane
Editor + Check

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.

Accept patchReject

Ready to ship your next plugin?

Set up Pressship in under a minute and stop fighting the WordPress.org publishing dance.

Get startedStar on GitHub