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.

⭐26stars🔀6forks📁View on GitHub🕐Updated Dec 29, 2025⬇️1downloads

When & Why to Use This Skill

The wp-project-triage skill provides a deterministic inspection of WordPress repositories, including plugins, themes, block themes, and core files. It generates structured JSON reports that identify project types, tooling, and testing configurations, enabling AI agents and developers to establish reliable workflow guardrails and understand environment conventions before making changes.

Use Cases

  • Automated Environment Discovery: Quickly identify the specific nature of a WordPress repository (e.g., Gutenberg vs. Block Theme) to apply the correct coding standards and commands.
  • Workflow Guardrails: Use the generated JSON report to programmatically prevent incompatible scripts or tools from running in a specific WordPress environment.
  • Tooling and Dependency Auditing: Automatically detect present PHP/Node.js tools, test suites, and version hints to ensure seamless integration and deployment workflows.
  • Pre-flight Checks for AI Agents: Provide a structured context for AI coding assistants to understand the repository structure and available commands before they attempt to modify code.
namewp-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 6.9+ (PHP 7.2.24+). 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.