wp-project-triage
wordpress/agent-skills
Deterministic inspection of WordPress repositories with structured JSON reports for workflow guidance.
What is wp-project-triage?
Analyzes a WordPress repository (plugin, theme, block theme, WP core, Gutenberg, or full site) to identify project kind, tooling, tests, and version hints. Outputs a structured JSON report to guide workflows and enforce guardrails before making changes.
- Detects project kind (plugin, theme, block theme, WP core, Gutenberg, full site)
- Identifies installed tooling (PHP, Node, build systems, test frameworks)
- Reports presence and type of tests (unit, integration, e2e)
- Extracts version hints from package.json, composer.json, and plugin/theme headers
- Generates structured JSON output matching triage.schema.json contract
- Provides signals for workflow selection and guardrail enforcement
How to install wp-project-triage
npx skills add https://github.com/wordpress/agent-skills --skill wp-project-triage- Node.js runtime available
- Bash shell access
- WP-CLI (optional, required for some workflows)
- WordPress 6.9+ target compatibility (PHP 7.2.24+)
How to use wp-project-triage
- 1.Run the detector from repo root: node skills/wp-project-triage/scripts/detect_wp_project.mjs
- 2.Capture the JSON output printed to stdout
- 3.Parse the JSON and check project.kind, signals, and tooling fields
- 4.Reference skills/wp-project-triage/references/triage.schema.json to understand the output contract
- 5.Use the report to select appropriate workflow guardrails and commands for your changes
- 6.Re-run after structural changes (adding theme.json, block.json, or build config)
Use cases
- Before modifying a WordPress plugin to understand its test setup and build tooling
- Analyzing a theme repository to determine if it's a block theme and what PHP/Node dependencies exist
- Inspecting WP core or Gutenberg checkouts to identify version and testing conventions
- Automating repository assessment in CI/CD pipelines to select appropriate workflows
- Guiding agent decision-making on which commands and conventions to follow
- AI agents (Claude Code, Cursor) working on WordPress projects
- Developers automating WordPress repository analysis
- CI/CD pipelines requiring deterministic project classification
- Teams enforcing consistent workflows across multiple WordPress repositories
wp-project-triage FAQ
Verify that you are running the command from the correct repository root. If the root is correct, the repository may not match recognized WordPress project patterns.
Large repositories with many files may take time to scan. You can optimize by adding or extending ignore directories in the detect_wp_project.mjs script.
WP-CLI is optional. The detector runs with bash and Node, but some workflows that use the triage report may require WP-CLI.
Re-run after changes that affect project structure or tooling, such as adding theme.json, block.json, or modifying build configuration.
The skill targets WordPress 6.9+ with PHP 7.2.24+. It can analyze repositories for those versions and above.
Full instructions (SKILL.md)
Source of truth, from wordpress/agent-skills.
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 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
- 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, andtooling. - 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.
Related skills
More from wordpress/agent-skills and the wider catalog.
wp-plugin-development
Develop WordPress plugins with architecture, hooks, security, and release guidance.
wp-rest-api
Build, extend, and debug WordPress REST API endpoints with schema validation, authentication, and custom fields.
wp-block-themes
Develop WordPress block themes with theme.json, templates, patterns, and Site Editor debugging.
wp-performance
Diagnose and optimize WordPress performance using WP-CLI profiling, Query Monitor, and targeted fixes.
wp-block-development
Develop WordPress Gutenberg blocks with block.json, registration, rendering, and deprecation workflows.
wordpress-router
Classify WordPress codebases and route to the correct workflow for plugins, themes, blocks, and core.