Wordpress Router

Before you touch a WordPress repo, this skill figures out what you're actually working with. It runs a triage script that detects whether you've got a plugin, theme, block theme, or core checkout, checks what tooling is present (Composer, @wordpress/scripts, PHPUnit, wp-env), then routes you to the right workflow based on your intent. The decision tree lives in a reference doc, so routing is consistent. Honestly, this is just good hygiene for any WordPress automation. If you skip classification and guess wrong, you'll waste time running the wrong build commands or missing required tests. One clarifying question beats ten minutes of backtracking.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 5
skills.sh installs: 6K
GitHub stars: 2.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wordpress/agent-skills --skill wordpress-router --agent claude-code

Installs into .claude/skills of the current project.

Files

WordPress Router

When to use

Use this skill at the start of most WordPress tasks to:

identify what kind of WordPress codebase this is (plugin vs theme vs block theme vs WP core checkout vs full site),
pick the right workflow and guardrails,
delegate to the most relevant domain skill(s).

Inputs required

Repo root (current working directory).
The user’s intent (what they want changed) and any constraints (WP version targets, WP.com specifics, release requirements).

Procedure

Run the project triage script:
- node skills/wp-project-triage/scripts/detect_wp_project.mjs
Read the triage output and classify:
- primary project kind(s),
- tooling available (PHP/Composer, Node, @wordpress/scripts),
- tests present (PHPUnit, Playwright, wp-env),
- any version hints.
Route to domain workflows based on user intent + repo kind:
- For the decision tree, read: skills/wordpress-router/references/decision-tree.md.
Apply guardrails before making changes:
- Confirm any version constraints if unclear.
- Prefer the repo’s existing tooling and conventions for builds/tests.