wordpress-router_skill

Overview

This skill classifies WordPress codebases and routes requests to the correct domain workflow. It quickly identifies whether a repo is a plugin, theme (classic or block), block theme, full site checkout, or WP core checkout and surfaces relevant tooling, tests, and version hints. Use it at the start of WordPress tasks to choose the right guardrails and delegate to specialized skills.

How this skill works

Run the included project triage script to detect project kind, available toolchains (PHP/Composer, Node, @wordpress/scripts), and test suites. Read the triage output to map primary project kinds and tooling, then consult the decision tree to pick the workflow to invoke. Before making changes, confirm version constraints and prefer the repo's existing build and test conventions.

When to use it

• At the start of any task touching a WordPress repository to determine routing.
• When the repo type is unclear (plugin vs theme vs full site vs WP core).
• Before running automated changes so the correct build/test commands are used.
• When you need to pick specialized workflows like blocks, theme.json, REST API, or packaging.
• When preparing a release or diagnosing CI/test failures tied to project structure.

Best practices

• Always run the triage script: node skills/wp-project-triage/scripts/detect_wp_project.mjs.
• Prefer the repository’s existing tooling and conventions for builds, tests, and packaging.
• Confirm WordPress version targets and platform-specific constraints before edits.
• Re-run triage after creating or moving significant files to keep classification accurate.
• If triage returns unknown, inspect root files: composer.json, package.json, style.css, block.json, theme.json, wp-content/.

Example use cases

• User asks to add a Gutenberg block to a repo: classify repo and route to blocks workflow.
• User requests performance improvements: detect theme vs plugin and route to performance checks.
• Prepare a release: verify packaging scripts and tests, then route to release packaging workflow.
• Security audit request: identify project kind and available test suites, then delegate to security checks.
• CI failing after restructuring: re-run triage, identify missing tooling hints, and suggest fixes.