Add wp-plugin-check skill (Plugin Check / PCP) + small wp-plugin-development guidance#64
Add wp-plugin-check skill (Plugin Check / PCP) + small wp-plugin-development guidance#64AndriusBurba wants to merge 1 commit into
Conversation
Adds a tightly-scoped wp-plugin-check skill that runs and interprets the official Plugin Check (PCP) tool (wp plugin check) against current WordPress.org standards: static vs runtime checks, filtering by category (security, performance, accessibility, i18n), reading errors vs warnings, and gating releases/CI. Routes fixes to the existing domain skills. Also adds small, factual guidance to wp-plugin-development: - a Dependencies & headers step (Requires Plugins header, WP 6.5+) - a pre-release Plugin Check step + verification bullets pointing to the new skill Includes the required eval scenario for the new skill. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @AndriusBurba. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
I've now linked my GitHub and WordPress.org accounts (@AndriusBurba). Flagging so the props list can refresh. |
1 participant
Summary
Adds a new, tightly-scoped
wp-plugin-checkskill that runs and interprets the official Plugin Check (PCP) tool against current WordPress.org standards, plus small factual additions towp-plugin-development.New skill:
wp-plugin-checkwp plugin check <slug>) -> optional runtime checks (--require) -> filter by category (security, performance, accessibility, i18n) -> interpret errors vs warnings -> re-run -> optional CI gating.wp-plugin-development,wp-performance,wp-phpstan,wp-plugin-directory-guidelines).--formatspellings (they change between releases); points towp plugin check --help.Small edits to
wp-plugin-developmentRequires Pluginsheader (WordPress 6.5+) and standard header requirements.This skill is self-contained (no
references/); a follow-up PR adds reference docs and router wiring.Why
The volume of plugin submissions has grown sharply, and Plugin Check is now the de-facto pre-submission quality gate. The skill set had no coverage of it. This partially addresses the planned
wp-testing/wp-securityskills.Test plan
node eval/harness/run.mjspasses (frontmatter + compatibility + triage).eval/scenarios/plugin-check-run-and-fix.json.wp plugin checkrun.