wp-project-triage/SKILL.md

---

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 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI."

---

Installed package paths (BB Skills adaptation, 2026-10-03)

Set BB_SKILL_DIR to the absolute directory containing this installed SKILL.md. For the default CLI destination, run export BB_SKILL_DIR="$PWD/.agents/skills/wp-project-triage" from your project root. If you chose another destination, assign that absolute folder instead. Keep the working directory at the WordPress project root when running the detector commands below; do not change into the skill directory. On PowerShell set $env:BB_SKILL_DIR and use $env:BB_SKILL_DIR in place of the Bash variable in command arguments.

Only helper command paths and this installation note are adapted. The unchanged original instructions are in upstream-original/SKILL.md; references, scripts and license notices retain their upstream bytes. These commands print inspection hints and do not run recommended build or database operations. Review the scripts before executing them.

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):
2. node "$BB_SKILL_DIR/scripts/detect_wp_project.mjs"
3. If you need the exact output contract, read:
4. triage.schema.json
5. Use the report to select workflow guardrails:
6. project kind(s)
7. PHP/Node tooling present
8. tests present
9. version hints and sources
10. 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.