wp-org-submission
Installation
SKILL.md
WordPress.org Plugin Submission & SVN Deploy
Model note: SVN deploy steps and asset setup are mechanical (
haiku). Pre-submission rejection-pattern scan across a real codebase (17 patterns) requires code judgment — usesonnet. Responding to a human reviewer rejection also needssonnet.
Get a plugin into the WP.org directory and keep releasing to it. Two distinct phases — know which one applies:
- Phase 1 — Initial submission. Plugin not yet in the directory. One-time human review, then SVN access is granted.
- Phase 2 — SVN deploy. Plugin already approved. Ship a new version into the existing SVN repo.
wp-org-submission is about the directory/SVN side. Sync the version sources first with [[wp-plugin-release]] — this skill assumes the codebase already carries the target version.
When to use
- "Submit this plugin to WordPress.org", "publish to the .org directory", "add my plugin to wp.org".
- "Deploy the new version to SVN", "push the release to wp.org", "tag a release on plugins.svn".
- "Set up screenshots / banner / icon", "why aren't my assets showing".
- "Fix a WP.org rejection", "respond to plugin review email", "they flagged trialware / source code / external service".
- Pre-submission hygiene sweep using the 17-issue rejection catalog (real reviewer quotes).