wp-org-submissionlisted

Use when submitting a WordPress plugin to the WP.org directory for the first time, deploying a new version via SVN (plugins.svn.wordpress.org trunk, tags, assets), fixing a reviewer rejection (17-issue catalog with exact reviewer quotes), writing or correcting readme.txt (Stable tag, Changelog, Upgrade Notice, Requires, Tested up to, External services), or preparing WP.org assets (banner-772x250.png, banner-1544x500.png, icon-128x128.png, icon-256x256.png, icon.svg, screenshot-N.png). Triggers: "submit my plugin to WP.org", "SVN deploy", "reviewer rejected my plugin", "fix WP.org review feedback", "how do I set up the SVN repo", "WP.org assets", "prepare my plugin for the directory", "what does the reviewer want", "Stable tag", "readme.txt requirements", "WP.org banner dimensions", "fix this reviewer comment", "plugin zip for submission", "svn commit trunk", "svn cp trunk tags", "reviewer says missing nonce", "reviewer says not prefixed", "reviewer says missing sanitization", "Upgrade Notice section", "Extern
mralaminahamed/wp-dev-skills · ★ 27 · Code & Development · score 77

Install: claude install-skill mralaminahamed/wp-dev-skills

# 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 — use `sonnet`. Responding to a human reviewer rejection also needs `sonnet`. 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). **Not for:** "will this pass WP.org review?", "check guideline violations", "is my plugin GPL-compliant?" — use the official `wp-plugin-directory-guidelines` skill for authoritative