Wp Project Triage

Before you start refactoring a WordPress repo, run this to get a deterministic JSON report of what you're actually dealing with. It scans for project type (plugin, theme, block theme, core, full site), detects PHP and Node tooling, finds tests, and pulls version hints so you know which conventions and commands to follow. The honest take: it's a pre-flight check that stops you from running the wrong build command or missing a composer setup. Targets WordPress 6.9+ and requires bash plus node, with some workflows needing WP-CLI. Rerun it whenever you add a theme.json or change build configs.

skills.sh installs: 347
GitHub stars: 211
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add automattic/agent-skills --skill wp-project-triage --agent claude-code

Installs into .claude/skills of the current project.

Files

WP Project Triage

When to use

Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.

Inputs required

Repo root (current working directory).

Procedure

Run the detector (prints JSON to stdout):
- node skills/wp-project-triage/scripts/detect_wp_project.mjs
If you need the exact output contract, read:
- skills/wp-project-triage/references/triage.schema.json
Use the report to select workflow guardrails:
- project kind(s)
- PHP/Node tooling present
- tests present
- version hints and sources
If the report is missing signals you need, update the detector rather than guessing.

Verification

The JSON should parse and include: project.kind, signals, and tooling.
Re-run after changes that affect structure/tooling (adding theme.json, block.json, build config).