wp-plugin-check + wp-plugin-development: reference docs and router wiring#65
Open
AndriusBurba wants to merge 2 commits into
Open
wp-plugin-check + wp-plugin-development: reference docs and router wiring#65AndriusBurba wants to merge 2 commits into
AndriusBurba wants to merge 2 commits 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>
…r wiring Moves depth out of the SKILL.md bodies into one-hop references, following the repo's authoring conventions: - wp-plugin-development/references/dependencies-and-headers.md: the Requires Plugins header (WP 6.5+) and standard header requirements. - wp-plugin-check/references/usage.md: Plugin Check categories, interpreting errors vs warnings (with a routing table to the domain skills), and CI usage. Also routes Plugin Check / PCP / pre-submission intent to wp-plugin-check from the wordpress-router decision tree. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
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 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. |
Author
|
I've now linked my GitHub and WordPress.org accounts (@AndriusBurba). Flagging so the props list can refresh. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #64. Moves depth out of the
SKILL.mdbodies into one-hopreferences/, per the repo's authoring conventions ("keep SKILL.md short; push depth into references").skills/wp-plugin-development/references/dependencies-and-headers.md— theRequires Pluginsheader (WordPress 6.5+) and standard header requirements, with upstream links; linked from the SKILL.skills/wp-plugin-check/references/usage.md— Plugin Check categories, interpreting errors vs warnings (with a routing table to the domain skills), and CI usage; linked from the SKILL.wp-plugin-checkfromwordpress-router's decision tree.Note on stacking
This branch is stacked on #64 (
wp-plugin-check-skill). Until #64 merges, this PR's diff againsttrunkwill also include #64's commit. Please review/merge #64 first.Test plan
node eval/harness/run.mjspasses.