mcpField
W
wp-project-triage

wp-project-triage

github.com/automatticDevelopment211342 installsUpdated 39w ago
Repository

About wp-project-triage

A skill that quickly identifies the kind of WordPress repository and its available tooling. It gives agents a structured report to choose suitable commands and workflow guardrails before making changes.

Key features

  1. 01Detect WordPress project kind
  2. 02Report tooling and test signals
  3. 03Identify version hints and sources
  4. 04Validate structured JSON output
  5. 05Re-run detection after project changes

Use cases

  1. 01Orienting before editing an unfamiliar WordPress repository
  2. 02Choosing commands based on available tools
  3. 03Checking how structural changes affect project detection

Install

Copy the command and run it in a terminal.

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

After installing, type/wp-project-triagein Claude Code to confirm it loaded.

Bundled filesreferences/triage.schema.jsonscripts/detect_wp_project.mjs

Details

From the project README

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.

Comments

Markdown supported