26 WordPress commands. You type one. Nothing else fires.

One Claude Code plugin for building, reviewing, migrating, and shipping WordPress plugins and themes. Each tool loads its procedure only when you call its slash command.

Commands

26

23 full toolkits, 3 guided helpers

Pickers

1

/wordpress-forge pages through every command

Bundled references & scripts

244

200 references, 44 scripts, loaded on demand

Auto-triggers

0

0 tokens in context until you call a tool

Procedure depth per tool

Lines of procedure and reference docs bundled in each lib/ folder

Commands by category

What each group of commands does

  • Build7

    Plugins, block themes, HTML to theme, mockups, demo content

  • Review & audit11

    Architect review, consulting audit, report card, grades, performance, security, theme standards, block code, exploit paths, plugin architecture, bug audit

  • Migrate & maintain5

    Classic to block, PSR-12 modernize, formatting, doc pass, WP-CLI fleet scripts

  • Ship3

    WordPress.org submission gate, feature README, demo video

All commands

Select a row to see what the tool does.

Command Tool Type

How a command runs

Procedures live in lib/, not skills/. Claude Code never discovers them, so no metadata sits in your context.

  1. 01You

    Type the command

    /wp-review ./my-plugin

    Anything after the name becomes the tool's argument.

  2. 02Command

    Read the "Load first" banner

    commands/wp-review.md

    Frontmatter sets disable-model-invocation: true.

  3. 03Procedure

    Load the procedure

    lib/wordpress-architect-review/SKILL.md

    Read at that moment, and at no other time.

  4. 04On demand

    Pull detail as needed

    references/ scripts/ examples/ sources/

    Rubrics, check lists, and runners load only when a step needs them.

# repo layout
.claude-plugin/
  marketplace.json     one plugin entry
  plugin.json          the wordpress-forge manifest
commands/              27 command files: 26 commands, 1 picker
lib/<tool>/
  SKILL.md             the procedure, read only when its command runs
  references/          deep detail, loaded on demand
  scripts/             deterministic runners
docs/wordpress.md      full write-up for every tool

Not sure which command? Run the picker.

/wordpress-forge pages all 26 commands over 9 screens.

pg 1/9
Command Which command?
    [Other] type a command name to jump straight to it

    Skip it: /wordpress-forge wp-format ~/themes/mytheme

    Guarantees

    Safety rules written into the procedures.

    Rule Where Status
    Nothing runs unless you type its command all 26 + picker Active
    Fleet scripts are a dry run until -f, then ask for a typed yes /wp-cli Active
    Review changes nothing. Build never overwrites. /wp-block-theme Active
    Only comments change, proven token by token against a backup /wp-doc-pass Active
    Theme files stay untouched unless you approve fixes /wp-bug-audit Active
    Nothing that changes data runs without approval. Your password never enters the chat. /wp-demo-video Active
    Never promises WordPress.org approval /wp-submission Verdict only

    Install

    Run these in any Claude Code session. One plugin, 26 commands and 1 picker, nothing running in the background.

    2 commands
    Install
    /plugin marketplace add chrismccoy/wordpress-forge
    /plugin install wordpress-forge@wordpress-forge
    Then
    /wordpress-forge          # browse every command
    /wp-plugin "Acme Bookings" # or call one directly