> **wp-project-triage** — skill 16 of 19 in [WordPress/agent-skills](https://skillsdocs.com/WordPress/agent-skills).
>
> Book (all skills, one file): https://skillsdocs.com/WordPress/agent-skills.md
> Machine manifest: https://skillsdocs.com/WordPress/agent-skills/.well-known/agent-skills/index.json
> Install the book: `npx skills add WordPress/agent-skills`
> Upstream: https://github.com/WordPress/agent-skills/blob/trunk/skills/wp-project-triage/SKILL.md @ `trunk`
> Raw bytes, no header: https://raw.githubusercontent.com/WordPress/agent-skills/trunk/skills/wp-project-triage/SKILL.md
> Base for relative paths: https://raw.githubusercontent.com/WordPress/agent-skills/trunk/skills/wp-project-triage/
> Licence: Other — https://github.com/WordPress/agent-skills
>
> Bundled files (2), referenced from this skill's directory:
>   - `references/triage.schema.json` — https://raw.githubusercontent.com/WordPress/agent-skills/trunk/skills/wp-project-triage/references/triage.schema.json
>   - `scripts/detect_wp_project.mjs` — https://raw.githubusercontent.com/WordPress/agent-skills/trunk/skills/wp-project-triage/scripts/detect_wp_project.mjs
>
> Content © its authors, served unmodified. Takedown: https://github.com/DreambaseAI/skillsdocs/issues/new?labels=takedown&title=Takedown+request

<!-- Verbatim upstream SKILL.md follows, YAML frontmatter included. -->

---
name: wp-project-triage
description: "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."
compatibility: "Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI."
---

# 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

1. Run the detector (prints JSON to stdout):
   - `node skills/wp-project-triage/scripts/detect_wp_project.mjs`
2. If you need the exact output contract, read:
   - `skills/wp-project-triage/references/triage.schema.json`
3. Use the report to select workflow guardrails:
   - project kind(s)
   - PHP/Node tooling present
   - tests present
   - version hints and sources
4. 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.