Methodologygeneric

wp-project-triage

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.

wordpress/agent-skills

View source

Install

npx skills add https://github.com/wordpress/agent-skills --skill wp-project-triage

Use with your agent

Install the wp-project-triage skill, then use it as build context. Run: npx skills add https://github.com/wordpress/agent-skills --skill wp-project-triage. Then read the installed skill.md and follow its guidance to build or refactor my project.

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.