wp-org-plugin-submissionlisted

Use when submitting a plugin to the WordPress.org plugin directory for the first time, or deploying a new version to an already-approved plugin via SVN (trunk/tags/assets, screenshots, banners, icons). Covers the pre-submission review checklist, readme.txt requirements, the git→SVN deploy flow, and how the Stable tag controls what users receive.
mralaminahamed/wp-dev-skills · ★ 3 · Code & Development · score 76

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

# WordPress.org Plugin Submission & SVN Deploy 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-plugin-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". ## Phase 1 — Initial submission The review is done by humans and can take days to weeks. Submitting a clean plugin avoids round-trips. 1. **Slug availability** — the directory slug is derived from the plugin name in the main file header. Pick a name not already taken at `https://wordpress.org/plugins/<slug>/` (404 = free). Slug is permanent. 2. **readme.txt valid** — must parse in the official validator: `https://wordpress.org/plugins/developers/readme-validator/`. Required header fields, valid `Stable tag`, GPL-compatible `License`. See `references/submission-checklist.md`. 3. **Guidelines compliance** — sanitize input, escape out