mralaminahamed/wp-dev-skills

wp-org-submission

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 correct…

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/mralaminahamed/wp-dev-skills --skill wp-org-submission

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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 18-guideline compliance review. This skill owns the workflow (SVN, assets, rejections); that skill owns the rules.

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 output, nonce-protect actions, prefix all globals, no obfuscation/minified-only code, no external loading of scripts, no tracking or calling home without explicit opt-in consent, GPL-compatible code + assets only. Full checklist in references/submission-checklist.md. 17-issue catalog with exact reviewer quotes in references/review-issues-catalog.md.
  4. Build a clean zip — source files (src/, composer.json, build configs) must be included; .wordpress-org/ and node_modules must not. Full include/exclude lists in §4 of references/submission-checklist.md.
  5. Submit at https://wordpress.org/plugins/developers/add/. The reviewer replies by email. Fix what they flag, reply briefly (context only, no change list), attach the updated zip. On approval, SVN access is granted at https://plugins.svn.wordpress.org/<slug>/.

Phase 2 — SVN deploy

WP.org distributes via Subversion, not git. The SVN repo has three top-level dirs:

<slug>/
├── trunk/        # current development copy of the plugin
├── tags/         # one immutable dir per released version (tags/1.2.0/)
└── assets/       # directory listing images — NOT shipped in the plugin zip

The `Stable tag` in `trunk/readme.txt` decides what users download — it must name a directory under tags/. Set Stable tag: 1.2.0 and ensure tags/1.2.0/ exists. (Pointing Stable tag at trunk is legal but discouraged — always release from a tag.)

Deploy = copy the production build into trunk/, then svn cp trunk tags/<version>, then commit. Use the helper:

bash
scripts/svn-deploy.sh <slug> <path-to-built-plugin-dir> <version>

It checks out SVN, syncs trunk/ to the build (adding/removing files), copies trunk → tags/<version>, and prints the svn commit to run after review. Full manual walkthrough and the add/delete handling in references/svn-deploy.md.

Assets (banner, icon, screenshots) live only in assets/, never in the zip. Exact filenames and dimensions are mandatory — banner-772x250.png, banner-1544x500.png (retina), icon-128x128.png, icon-256x256.png, icon.svg, screenshot-1.png (matched to the 1. line under == Screenshots == in readme.txt). See references/svn-deploy.md.

Top rejection patterns

Most frequent — not exhaustive. Full 17-issue catalog with exact reviewer quotes in references/review-issues-catalog.md.

  • Generic or trademarked slug; "WordPress"/"Woo" in the plugin name.
  • Main PHP file name doesn't match the slug (plugin.php instead of <slug>.php).
  • Invalid URLs in plugin header or readme.txt — verify with curl -I before submission.
  • External service called but not documented in == External services ==.
  • Unsanitized $_GET/$_POST, unescaped output, missing nonces + capability checks.
  • Loading JS/CSS from a CDN instead of bundling; inline <style> / <script> tags.
  • No source for compiled output — src/ not in zip and no public repo linked.
  • .wordpress-org/ or node_modules/ in the zip.
  • Generic function/class prefix or mixed prefixes across one plugin.
  • Trialware (Guideline 5) — features gated behind license key or Pro plan check. See references/trialware-compliance.md.
  • Admin notices on every screen, persistent nags, full-page upsell flows (Guideline 11).
  • Stable tag names a tag that doesn't exist under tags/ → users get nothing.

References

  • references/submission-checklist.md — comprehensive pre-submission checklist (identity, readme.txt, guidelines, zip hygiene, security pattern, automated checks).
  • references/review-issues-catalog.md — 17-issue catalog with exact reviewer quotes and corrective actions, sourced from 8 real submissions.
  • references/trialware-compliance.md — Guideline 5 freemium pattern, audit checklist, and step-by-step licensing-layer removal.
  • references/svn-deploy.md — complete SVN workflow, asset spec, Stable-tag mechanics, hotfix flow.
  • scripts/svn-deploy.sh — git/build → SVN trunk+tag deploy helper.
  • Official: wp-plugin-directory-guidelines (WordPress/agent-skills) — authoritative source for the 18 WP.org Plugin Directory guidelines; use it for GPL/naming/trialware rule interpretation when our 17-issue catalog conflicts or is ambiguous.
같은 저장소의 Skills

더 많은 Skills

모든 Skills
mralaminahamed
커뮤니티

wp-admin-browser

Use when a WordPress admin panel needs real browser interaction via Chrome DevTools MCP — logging in, navigating admin menus, clicking buttons, filling and submitting forms, creating/editing/deleting content through the UI, creating a temporary test admin user, verifying JS state or localStorage, capturing screenshots, or obtaining a REST nonce via admin-ajax.php. Triggers: \"open WP admin\", \"log in to WordPress\", \"navigate to Settings\", \"create a test user in admin\", \"click Save Changes

1시간 설치 수
1
GitHub Stars
29
업데이트
7월 20일
mralaminahamed
커뮤니티

wp-build-tools

Use when setting up, configuring, or debugging the JavaScript/CSS build pipeline for a WordPress plugin — @wordpress/scripts, webpack (webpack.config.js, entry points, externals), Vite, block editor asset compilation with block.json, enqueueing built assets with .asset.php dependency files, wpenqueuescript / wplocalizescript, Sass/SCSS/PostCSS compilation, TypeScript support, registerblocktype, or reusing a JS/CSS library already bundled by a host plugin (EDD, WooCommerce, Elementor). Triggers:

1시간 설치 수
1
GitHub Stars
29
업데이트
7월 20일
mralaminahamed
커뮤니티

wp-ci-qa

Use when a pull request has QA failures, a \"Testing Failed\" label, or QA comments reporting broken features — reading QA feedback and PR comments, tracing root cause using root-cause-patterns.md, applying scoped conventional-commit fixes, swapping labels (Testing Failed to Need Testing), and posting a structured QA re-test comment. Triggers: \"QA failed my PR\", \"Testing Failed label on my PR\", \"fix the QA comments on PR\", \"QA says feature X is broken\", \"post a re-test comment\", \"how

1시간 설치 수
1
GitHub Stars
29
업데이트
7월 20일