Install for your agent

1. Get the pack

Install Git and Python 3.10+ and choose an agent you already have access to. Clone the source and run the remaining installation commands from that checkout.

git clone https://github.com/ehsanenaloo/wordpress-devkit.git
cd wordpress-devkit
python --version

2. Choose one installation mode

Claude plugin session

Use this when you want the namespaced slash commands. Replace the path with your actual checkout.

claude --plugin-dir "C:\path\to\wordpress-devkit"

This loads the plugin for that CLI session. Cloning alone does not register a plugin, and this flag does not configure a desktop app. Verify available commands in the session you will use.

Google Antigravity

For a native plugin, download wp-devkit-antigravity-<version>.zip from the Releases page and extract it first. In Antigravity CLI, install the extracted directory:

agy plugin install "C:\path\to\wp-devkit"
agy plugin list

For Antigravity 2.0 or standalone IDE, place the extracted wp-devkit folder under your target project's .agents/plugins/, or under ~/.gemini/config/plugins/ for all projects. Check active skills in Customizations. Use one installation method per scope.

For manual skills, the regular DevKit installer defaults to ~/.gemini/config/skills:

python scripts/install.py --agent antigravity --preview
python scripts/install.py --agent antigravity

For CLI global skills, pass --destination "~/.gemini/antigravity-cli/skills". For workspace skills, pass the target WordPress project's .agents/skills directory. Keep it outside the source checkout. PowerShell accepts -Agent antigravity; selection, status, updates and removal share the existing options.

Start a new conversation and request wp-devkit-security-review by name. Antigravity 2.0 and CLI also support /wp-devkit-security-review. The Claude namespaced commands remain Claude-specific. Google's plugin guide and skill guide describe client setup. File checks do not prove actual client loading.

Manual skills for Codex

Preview the complete skill directories, then install them. The default is ~/.codex/skills.

python scripts/install.py --agent codex --preview
python scripts/install.py --agent codex

Manual skills for Claude

The default is ~/.claude/skills. Manual skills do not add the plugin slash commands.

python scripts/install.py --agent claude --preview
python scripts/install.py --agent claude

On platforms where the interpreter is named python3, use that name. PowerShell users can alternatively run .\scripts\install.ps1 -Agent codex or select claude.

3. Verify activation in your target project

Open the WordPress project you want to review. In Codex, explicitly select the installed skill or request it by name:

$wp-devkit-site-audit-and-onboarding
Read this project’s instructions, classify its stack and propose the next review.
Do not edit files or run project bootstrap code.

Ask the agent to read the chosen workflow and its engineering contract. Installed files alone do not establish that the current session loaded them.

Custom destinations

Choose a skills directory outside the DevKit checkout. A custom CODEX_HOME needs an explicit destination; the installer’s default does not discover it.

python scripts/install.py --agent codex --destination "C:\path\to\custom-codex-home\skills" --preview
python scripts/install.py --agent codex --destination "C:\path\to\custom-codex-home\skills"

Update, remove or recover

If named DevKit directories already exist, preview first and use the same destination as the original install. The installer refuses to replace or remove a skill that has local edits, or a directory DevKit did not install, unless you copy what you want to keep and add --force. Check with --status.

python scripts/install.py --agent codex --destination "C:\path\to\skills" --preview
python scripts/install.py --agent codex --destination "C:\path\to\skills" --replace

To uninstall, inspect the preview, then explicitly remove only the named DevKit directories:

python scripts/install.py --agent codex --destination "C:\path\to\skills" --uninstall --confirm

If rollback fails, inspect retained workspaces and restore the appropriate one. Replace the workspace placeholder with an actual listed name.

python scripts/recover_distribution.py --destination "C:\path\to\skills"
python scripts/recover_distribution.py --destination "C:\path\to\skills" --restore .wp-devkit-<workspace>

If that lists nothing but an install still fails with a lock message, no installation is running and the lock can be cleared:

python scripts/recover_distribution.py --destination "C:\path\to\skills" --clear-stale-lock

ChatGPT and Codex plugin

Extract the package first. Its root plugin.json discovers all 20 complete skills in skills/. The included .agents/plugins/marketplace.json points to that root and exposes WordPress DevKit for installation.

ChatGPT desktop

1. Open the extracted wp-devkit folder as your project in Work mode or Codex.
2. Restart the desktop app, then open Plugins Directory.
3. Choose WordPress DevKit and install wp-devkit.
4. Start a new chat and select the skill for your task.

This local workflow requires plugin support in your client. ChatGPT web and workspace publication use separate supported setup paths.

Codex marketplace setup

With a CLI that supports plugin marketplaces, register the extracted package root:

codex plugin marketplace add "C:\path\to\wp-devkit"
codex plugin marketplace list

Registration makes the catalog available. If codex plugin --help lists add, install with:

codex plugin add wp-devkit@wordpress-devkit

The locally inspected CLI supports this selector. For clients without that command, use desktop installation or the manual skill installation earlier in this guide. Check skill selection in a new session. The package has no connected service, account login or automatic enablement. After an update, refresh or reopen the marketplace and check the installed copy in a new chat.

These steps follow the official OpenAI setup guide. Package validation checks file structure and resource paths; actual client loading remains a separate check.