Skip to main content

Home/AI agents

pressship.org/ai

The WordPress.org publishing
runbook — for agents and humans.

Agents fetch this URL; you can just read it. Same bounded runbook either way: verify, package, dry-run, then confirm before mutating remote state. No improvised commands.

Give this to your agent:

Agents that prefer raw text can fetch /ai.txt. This page is the same runbook, made readable for people.

Open plain textAgent skill guide
The runbook

The same steps, for agent or hand.

One predictable order: inspect, validate, package, and dry-run before anything leaves the machine.

pressship.org/aifetchable

  1. Identify the plugin root

    Don't assume the repository root is the plugin root when multiple plugins or build outputs exist.

  2. Check the account and route

    $npx pressship whoami$npx pressship info .$npx pressship status .

  3. Validate before packaging

    $npx pressship verify .

  4. Package after validation

    $npx pressship pack .

  5. Dry-run before any mutation

    $npx pressship publish . --dry-run -y

  6. Ask before mutating remote state

    Pause before any upload, reupload, SVN commit, release tag, or git change.

    Human approval required
Route selection

The dry run detects the route.

Pressship reads the plugin's WordPress.org state and chooses the safe path automatically.

New pluginnpx pressship publish . --dry-run -y

Prepares a WordPress.org submission upload.

Pending reviewnpx pressship publish . --dry-run -y

Prepares a reupload of the review package.

Approvednpx pressship publish . --release --dry-run -y

Prepares an SVN release through trunk and tags.

Human checkpoints

Agents pause for approval — and you should pause too — before:

  • Uploading or reuploading to WordPress.org.
  • Committing to SVN or creating release tags.
  • Changing git commits, branches, tags, or remotes.
  • Using --no-verify or bypassing validation.
  • Treating Plugin Check warnings as acceptable.
  • Publishing from a generated build folder when the source root is unclear.

Final report

When the work is done, the agent reports back:

  • Whether verify ran.
  • Whether a publishing dry run ran.
  • Plugin Check result summary.
  • Package size and notable included or excluded files.
  • Selected route: new submission, reupload, or SVN release.
  • Upload or release status and slug, if mutation was approved.
  • Whether git and SVN were left untouched or changed.
Useful docs

Go deeper.

The same workflow is documented for people, with command references and setup guides.

Agent skill guideInstall the dry-run-first publishing skill.Getting startedSet up Pressship and authenticate.Publish commandHow route detection and dry runs work.Pack commandValidation, Plugin Check, and zip output.

Follow the path, by agent or by hand.

Install the skill once, hand your agent the prompt above, or simply work through the steps yourself.

Read the skill guideGetting started