Agent-skills wp-project-triage

Name: wp-project-triage
Author: WordPress

Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.

install

source · Clone the upstream repo

git clone https://github.com/WordPress/agent-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/WordPress/agent-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/wp-project-triage" ~/.claude/skills/wordpress-agent-skills-wp-project-triage && rm -rf "$T"

manifest: skills/wp-project-triage/SKILL.md

source content

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).

Failure modes / debugging

If it reports
```
unknown
```
, check whether the repo root is correct.
If scanning is slow, add/extend ignore directories in the script.