Skill

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.

npx claudepluginhub pleaseai/claude-code-plugins --plugin wordpress

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.

SKILL.md

Similar Skills

wp-project-triage

1.3k

Detects WordPress repo type (plugin/theme/block theme/WP core/Gutenberg/full site), scans for tooling/tests/versions, outputs structured JSON to guide workflows and guardrails.

2 files

wordpress-agent-skills-9

diagnostic-code-quality

Analyzes code quality in custom WordPress themes and plugins using two-pass approach: quick grep scans for deprecated functions and anti-patterns, then AI contextual review of flagged PHP/JS files.

wordpress-expert

wp-pr-review

Reviews WordPress plugin PRs for security, performance, WPCS standards, and backward compatibility using GitHub/GitLab tools or local git diffs. For WP plugin code reviews and audits.

7 files13 tools

jaan-to

Stats

Parent Repo Stars5

Parent Repo Forks1

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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, 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.