About wp-project-triage
A triage skill for developers who need to understand a WordPress repository before making changes. It detects project types and tooling, then uses the report to guide workflow choices and verification.
Key features
- 01Detect WordPress project signals
- 02Report project kinds and tooling
- 03Guide workflow and guardrail selection
- 04Verify detector output
Use cases
- 01Identify the type of an unfamiliar repository
- 02Check available PHP and Node tooling
- 03Choose relevant tests before editing
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ wordpress/ agent-skills --skill wp-project-triageAfter installing, type/wp-project-triagein Claude Code to confirm it loaded.
Bundled filesreferences/triage.schema.jsonscripts/detect_wp_project.mjs
Details
From the project READMEWP 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, andtooling. - 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.
Comments
Markdown supported