feat: package as Claude Code plugin (wordpress-api-pro) 🤖#16
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@codex review |
|
Codex Review: Didn't find any major issues. Swish! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
…ons + Codex P2)
- Update plugin author to studio-neutral { "name": "Digitizer" } (owner decision)
- Replace Windows note with pre-clone config guidance + checkout repair steps (Codex P2)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4b143e2f80
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `git config --global core.symlinks true` **before** cloning or installing — | ||
| the plugin cache clone inherits it. Changing the config does not repair an | ||
| existing checkout (the repo may have recorded `core.symlinks=false` locally): | ||
| inside it run `git config core.symlinks true && git checkout -- .`, or |
There was a problem hiding this comment.
Limit the checkout repair to the symlink files
For an existing Windows checkout containing any uncommitted tracked edits, git checkout -- . selects every path under the repository and overwrites those edits while repairing the links. As reflected by git checkout -h ([<branch>] -- <file>...), the argument after -- is a file pathspec, and . covers the whole worktree. Restrict this command to .claude/skills/wordpress-api-pro and skills/wordpress-api-pro (ideally after checking git status) so the documented repair does not cause unrelated data loss.
Useful? React with 👍 / 👎.
… P2) The repair instruction used `&&` (unsupported in PowerShell 5.1) and a repo-wide `git checkout -- .`, which silently discards uncommitted edits everywhere. Now two separate commands, with the checkout scoped to `skills/` so only the symlink entry is re-materialized and the rest of the working tree is untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1d531ea709
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ``` | ||
|
|
||
| Then restart Claude Code, export `WP_URL` / `WP_USERNAME` / `WP_APP_PASSWORD` (or set up `config/sites.json`), and ask Claude to use it. The ACF / SEO / JetEngine / plugin-detection scripts need `requests` (`pip install requests`); the core post/page/media/WooCommerce/batch scripts use the Python stdlib only. | ||
| ### Windows note |
There was a problem hiding this comment.
Restore the documentation displaced by the Windows note
This replacement leaves the README ending immediately after the Windows note and removes roughly 300 lines of user-facing material, including setup requirements, environment configuration, quick-start commands, safety guidance, script documentation, and the ClawHub release procedure. Plugin packaging does not make those repository instructions obsolete, so retain the existing sections and insert the Windows guidance without truncating everything that followed the Claude Code installation block.
Useful? React with 👍 / 👎.
| "agent-skills@digitizer-skills": true, | ||
| "cloudways-mcp@digitizer-skills": true, | ||
| "hostinger-mcp@digitizer-skills": true, |
There was a problem hiding this comment.
Remove unrelated plugins from the project configuration
In a checkout of this standalone WordPress plugin, these project-scoped settings enable the entire marketplace suite—including hosting, ads, Aura, and Sumit plugins—even though repo-wide search shows no dependency on them. Contributors who have those plugins installed will therefore activate unrelated MCP integrations whenever they open this repository; keep only this project's required plugin entries, or leave personal marketplace selections in local settings.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Deliberate, spec-mandated (same as the sibling repos): the committed settings block declares the full Digitizers toolbox in every toolbox repo so team cloud/phone sessions load it everywhere. Claude Code prompts per user before activating project-declared plugins — nothing activates silently.
…dex P2) The automated v3-note swap truncated from the note header to end of file, deleting every section that followed it (quick start, env setup, script docs, release procedure / links and footer). Rebuilt from the pre-v3 revision with only the Windows-note section replaced by v3. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…odex P2) The scoped checkout fixed skills/ but left .claude/skills/<name> as a plain file on symlink-less checkouts (reproduced by the reviewer), so cloud-session discovery stayed broken after "repair". The command now re-materializes both entries; where .claude/skills/<name> is the real source directory the extra path is a no-op. cloudways also gains set -euo pipefail in the no-leak guard step so a missing perl or grep error fails CI loudly instead of passing silently. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@codex review |
|
Codex Review: Didn't find any major issues. Can't wait for the next one! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
Package wordpress-api-pro as a Claude Code plugin with proper symlink structure and marketplace configuration.
.claude-plugin/plugin.jsonwith plugin metadataskills/wordpress-api-pro→../wordpress-api-proand.claude/skills/wordpress-api-pro→../../wordpress-api-pro.claude/settings.jsonwith marketplace and enabled plugins configurationThis allows the skill to be installed and used as a Claude Code plugin.
🤖 Generated with Claude Code