Wp Project Triage

Before you start refactoring a WordPress repo or setting up CI, 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), checks what tooling is present (Composer, npm, webpack), looks for tests, and pulls version hints from headers and manifests. The schema is documented, so you can wire it into workflows or guardrails without guessing. It's especially useful if you're building agents or scripts that need to adapt behavior based on repo structure. If it reports "unknown" you're probably in the wrong directory, and if you need signals it doesn't catch yet, you're meant to extend the detector script rather than work around it.

skills.sh installs: 5.9K
GitHub stars: 2.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wordpress/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).