feat(wordpress): add WordPress plugin to marketplace#137
Conversation
Add WordPress plugin with expert-level knowledge for blocks, themes, plugins, and best practices. Includes marketplace registration, README documentation, and release-please configuration.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
10 issues found across 84 files
Confidence score: 3/5
- There is a concrete behavior risk in
plugins/wordpress/.agents/skills/wp-plugin-development/scripts/detect_plugins.mjs: scanning the full PHP file forPlugin Name:can falsely classify non-plugin files, which can misroute automation decisions. - A second functional detection gap in
plugins/wordpress/.agents/skills/wp-project-triage/scripts/detect_wp_project.mjs(missing* Plugin Name:PHPDoc-style headers) may cause real plugins to be skipped during triage. - Most other findings are documentation/command-path issues (for example in
plugins/wordpress/.agents/skills/wp-performance/SKILL.md,plugins/wordpress/.agents/skills/wordpress-router/SKILL.md, andplugins/wordpress/.agents/skills/wp-plugin-development/SKILL.md), which are lower severity but can still break user workflows if copied verbatim. - Pay close attention to
plugins/wordpress/.agents/skills/wp-plugin-development/scripts/detect_plugins.mjsandplugins/wordpress/.agents/skills/wp-project-triage/scripts/detect_wp_project.mjs- plugin detection accuracy can produce false positives or miss valid plugins.
Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="plugins/wordpress/.agents/skills/wp-plugin-development/scripts/detect_plugins.mjs">
<violation number="1" location="plugins/wordpress/.agents/skills/wp-plugin-development/scripts/detect_plugins.mjs:81">
P2: Plugin header parsing scans the entire PHP file, so non-plugin files with `Plugin Name:` anywhere can be falsely detected as plugins.</violation>
</file>
<file name="plugins/wordpress/.agents/skills/wp-performance/references/wp-cli-profile.md">
<violation number="1" location="plugins/wordpress/.agents/skills/wp-performance/references/wp-cli-profile.md:26">
P2: The example over-escapes quotes inside a single-quoted shell string, so WP-CLI receives `do_action(\"init\");` which is invalid PHP. Use unescaped double quotes inside the single-quoted argument.</violation>
</file>
<file name="README.md">
<violation number="1" location="README.md:243">
P3: Manual installation list omits the newly added WordPress plugin, so bulk install guidance is inconsistent with the Available Plugins section.</violation>
</file>
<file name="plugins/wordpress/.agents/skills/wp-performance/SKILL.md">
<violation number="1" location="plugins/wordpress/.agents/skills/wp-performance/SKILL.md:45">
P2: The skill doc references `skills/wp-performance/scripts/perf_inspect.mjs`, but the script is shipped under `.agents/skills/wp-performance/scripts/perf_inspect.mjs`. As written, the command path won’t resolve from the plugin root, breaking the workflow.</violation>
</file>
<file name="plugins/wordpress/.agents/skills/wordpress-router/SKILL.md">
<violation number="1" location="plugins/wordpress/.agents/skills/wordpress-router/SKILL.md:25">
P2: This step references a triage script that isn’t present in the repo, so anyone following the skill will hit a broken command. Update the instruction to point at the correct script path (or add the script).</violation>
</file>
<file name="plugins/wordpress/.agents/skills/wp-project-triage/SKILL.md">
<violation number="1" location="plugins/wordpress/.agents/skills/wp-project-triage/SKILL.md:20">
P2: Procedure paths point to `skills/...` even though the skill is located under `.agents/skills/...` in this plugin, so the documented detector command and schema path will not resolve.</violation>
</file>
<file name="plugins/wordpress/.agents/skills/blueprint/SKILL.md">
<violation number="1" location="plugins/wordpress/.agents/skills/blueprint/SKILL.md:311">
P3: Conflicting guidance: earlier the doc says `installPlugin` accepts DirectoryReferences (e.g., `git:directory`, `literal:directory`) without zipping, but later it claims `installPlugin` “expects a zip.” This inconsistency can mislead blueprint generation for bundled resources.</violation>
</file>
<file name="plugins/wordpress/.agents/skills/wp-performance/references/server-timing.md">
<violation number="1" location="plugins/wordpress/.agents/skills/wp-performance/references/server-timing.md:17">
P3: The example command escapes quotes inside an unquoted shell argument, so rg receives a pattern containing literal quotes ("^server-timing:") and may not match real Server‑Timing headers. Remove the escaped quotes or use proper single quotes.</violation>
</file>
<file name="plugins/wordpress/.agents/skills/wp-project-triage/scripts/detect_wp_project.mjs">
<violation number="1" location="plugins/wordpress/.agents/skills/wp-project-triage/scripts/detect_wp_project.mjs:127">
P2: Plugin header regex misses PHPDoc-style `* Plugin Name:` lines, so real plugins using standard starred headers won’t be detected.</violation>
</file>
<file name="plugins/wordpress/.agents/skills/wp-plugin-development/SKILL.md">
<violation number="1" location="plugins/wordpress/.agents/skills/wp-plugin-development/SKILL.md:31">
P2: The documented triage commands reference `skills/...` paths that don’t exist in this repo; the scripts live under `plugins/wordpress/.agents/skills/...`, so these commands will fail and block the workflow.</violation>
</file>
Architecture diagram
sequenceDiagram
participant U as User
participant AI as AI Assistant (Claude)
participant R as NEW: WordPress Router
participant T as NEW: WP Project Triage
participant FS as Local Filesystem (WP Repo)
participant DS as NEW: Domain Skills (Blocks, Perf, REST, etc.)
participant CLI as System (Node.js / WP-CLI)
Note over U,CLI: Workflow for WordPress-related coding tasks
U->>AI: "Analyze this WordPress project"
AI->>R: NEW: Route task to WordPress plugin
rect rgb(240, 240, 240)
Note right of R: Project Identification Phase
R->>T: NEW: Invoke triage skill
T->>CLI: NEW: Execute detect_wp_project.mjs
CLI->>FS: Scan for wp-config.php, block.json, etc.
FS-->>CLI: File presence & metadata
CLI-->>T: JSON project report
T-->>R: Return classification (e.g., wp-block-theme)
end
alt Intent: Performance Optimization
R->>DS: NEW: Select wp-performance skill
DS->>CLI: NEW: Execute perf_inspect.mjs
opt If environment permits
CLI->>CLI: Invoke 'wp profile' / 'wp doctor'
end
CLI-->>DS: JSON performance metrics
else Intent: Block Development
R->>DS: NEW: Select wp-block-development skill
DS->>CLI: NEW: Execute list_blocks.mjs
CLI->>FS: Parse block.json files
CLI-->>DS: List of blocks & apiVersions
end
DS-->>R: Recommended actions/analysis
R-->>AI: Formulated expert response
AI-->>U: Final technical guidance
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
The Available Plugins section added the WordPress plugin but the manual installation code block was not updated to include it, making the bulk install guidance inconsistent.
There was a problem hiding this comment.
Code Review
This pull request adds a comprehensive WordPress plugin to the marketplace, featuring a wide array of specialized agent skills for tasks such as block development, performance profiling, and REST API management. The review feedback identifies several opportunities to improve the project triage script, including adding error handling for directory reads, refining regex patterns for configuration constant detection, and using relative paths in reports to ensure portability and avoid leaking local filesystem structures.
|
✅ @amondnet님의 요청을 완료했습니다 (56s) —— View job PR Review Status SummaryThanks for the update, @amondnet! README.md fix is confirmed applied in Review Issues Summary
All P2/P3 issues in The gemini-code-assist suggestions for The PR looks good for merge — the only locally applicable fix has been applied. |
Summary
marketplace.json)release-pleaseconfiguration for versioningChanges
The WordPress plugin provides knowledge for:
Test Plan
/plugin install wordpress@pleaseaiSummary by cubic
Adds a new
wordpressplugin to the marketplace that provides expert, task-focused guidance for WordPress development and ops. It registers the plugin inmarketplace.json, updates README docs (including the manual install list), and configuresrelease-pleasefor versioning.New Features
wordpresswith skills for blocks, block themes, plugin development, REST API, Interactivity API, performance, WP-CLI/ops, PHPStan, Playground, Abilities API, and WPDS.Migration
/plugin install wordpress@pleaseai.Written for commit dc37361. Summary will update on new commits.