Wp Project Triage

1---
2name: wp-project-triage
3description: "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."
4compatibility: "Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI."
5---
6 
7# WP Project Triage
8 
9## When to use
10 
11Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.
12 
13## Inputs required
14 
15- Repo root (current working directory).
16 
17## Procedure
18 
191. Run the detector (prints JSON to stdout):
20   - `node skills/wp-project-triage/scripts/detect_wp_project.mjs`
212. If you need the exact output contract, read:
22   - `skills/wp-project-triage/references/triage.schema.json`
233. Use the report to select workflow guardrails:
24   - project kind(s)
25   - PHP/Node tooling present
26   - tests present
27   - version hints and sources
284. If the report is missing signals you need, update the detector rather than guessing.
29 
30## Verification
31 
32- The JSON should parse and include: `project.kind`, `signals`, and `tooling`.
33- Re-run after changes that affect structure/tooling (adding `theme.json`, `block.json`, build config).
34 
35## Failure modes / debugging
36 
37- If it reports `unknown`, check whether the repo root is correct.
38- If scanning is slow, add/extend ignore directories in the script.
39