Repository navigation
Fix skill catalog drift in CI, router, and eval coverage - #98
NoumaanAhamed wants to merge 2 commits into
Conversation
|
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. |
There was a problem hiding this comment.
The solution here is likely ditching the -v1 slop from the doc (or ditching this entire file as ai-slop), but if not, then it begs the question what makes these new skills part of a "v1"?
| - Route → `wp-performance`. | ||
| - **Security / nonces / capabilities / sanitization/escaping / uploads** | ||
| - Route → `wp-security` (planned). | ||
| - Route → `wp-plugin-development` (already covers this today); a dedicated `wp-security` split-out is planned but not yet implemented. |
There was a problem hiding this comment.
This is not an AI-decision log. Either it should route to somewhere specific or it shouldn't because it's "planned". but if it's "already covered", then there is 0 human reason to include that it's covered (self-documenting) or potential future refactor plans.
Title:
Summary
.github/workflows/ci.ymlnow loops over everyskills/*/directory forskills-ref validateinstead of a hardcoded 10-skill list — 8 skills (blueprint,wp-abilities-audit,wp-abilities-verify,wp-patterns,wp-phpstan,wp-plugin-directory-guidelines,wp-rest-api,wpds) were shipping with zero CI schema validationskills/wordpress-router/references/decision-tree.mdgains routes forwpds,wp-abilities-audit,wp-abilities-verify,wp-patterns, andwp-plugin-directory-guidelines— previously dead ends with no routewp-plugin-development(which already covers nonces/capabilities/sanitization) instead of the nonexistentwp-securityeval/scenarios/wpds-build-component-with-tokens.json—wpdshad zero eval coverageTest plan
node eval/harness/run.mjspassescommdiff againstls skills)eval/scenarios/wpds-build-component-with-tokens.jsonvalidated as well-formed JSON matching the scenario schemaCloses #97