wp-project-triage

Detect WordPress repository type and tooling, outputting a JSON triage report.

14|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wpgaurav/WordPress-skills --skill wp-project-triage-wpgaurav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-project-triage
Source: https://github.com/wpgaurav/WordPress-skills/tree/main/skills/wordpress/wp-project-triage
Command: npx skills add https://github.com/wpgaurav/WordPress-skills --skill wp-project-triage-wpgaurav

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Quickly identify the WordPress repository type (plugin, theme, block, core, or full-site) and surface the commands, tooling, and conventions you should follow before making changes.

Core Features & Use Cases

  • Deterministic repo detection: classifies the project kind and essential characteristics to tailor workflows.
  • Tooling & tests discovery: detects PHP/Node tooling, tests suites, and version hints to guide setup.
  • Structured triage report: outputs a JSON document describing project.kind, signals, and available tooling to drive guardrails.
  • Use Case: Before contributing a patch, run the detector to understand required checks and recommended next steps.

Quick Start

Run the detector to print a structured JSON triage report for the current repository.

Frequently Asked Questions about wp-project-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify a WordPress repository type before making changes?

To identify a WordPress repository type, run a deterministic detector script that classifies the project as a plugin, theme, block, WP core, or full-site project. The detector analyzes repository signals and outputs a structured JSON triage report detailing the project kind and available tooling.

What tooling and tests should I check before contributing to a WordPress plugin or theme?

Before contributing to a WordPress plugin or theme, check for PHP and Node tooling, test suites, and version hints. Running a repository triage detector surfaces these tooling signals in a structured JSON report, ensuring you follow required conventions and setup steps.

Can I use the WordPress triage detector for full-site and block projects?

Yes, the WordPress triage detector can be used for full-site and block projects. It deterministically classifies project kinds including plugins, themes, blocks, WP core, and full-site projects, surfacing project characteristics and tooling presence to guide safe code changes.

What is the best way to automate WordPress project classification and guardrail generation?

The best way to automate WordPress project classification is running a deterministic detector script that analyzes repository signals. It outputs a structured JSON triage report matching a specific schema with project kind, detected signals, and tooling details to drive workflow guardrails.

How do I get a structured JSON report of my WordPress repository signals and tooling?

Run the WordPress project detector script in your repository to print a structured JSON triage report. This report matches the triage schema and includes project kind, detected signals, and available tooling to guide your development workflow and guardrails.

Why do I need to run a repository detector before patching a WordPress project?

Running a repository detector before patching a WordPress project identifies its kind and required tooling. This ensures you understand the necessary checks, test suites, and conventions, preventing unsafe changes and guiding your setup with a structured triage report.