wp-hooks-graph

Strategy for finding conflicts between two WordPress codebases (plugin↔plugin, plugin↔theme, plugin↔core) via the `hooks-graph` MCP server. Use whenever the user wants to compare, diff, audit, or find conflicts/collisions/clashes/interference between two repos, plugins, themes, or codebases — including phrases like "do these two plugins conflict", "find overlap between X and Y", "what hooks do A and B share", "where will plugin X step on plugin Y", "audit integration risk between these repos", "priority conflicts", "callback collisions", or any request to compare two parsed codebases in `~/.hooksgraph/codebases/`. Apply this skill even if the user names only "conflicts" without saying "hooks" — in WordPress, cross-plugin conflicts almost always surface through the hook system.

Strategy for triaging a WordPress issue/bug report against a list of active plugins by finding likely cross-plugin conflicts. Use whenever the user describes a site issue (bug, regression, broken feature, "X stopped working", "checkout is failing", "posts aren't saving", "REST endpoint returns wrong data") and provides — or can provide — the list of active plugins/themes, asking which plugins are conflicting or likely responsible. Trigger phrases include "which plugin is causing this", "find the conflict from this issue", "triage this bug across the active plugins", "narrow down the culprit", "audit the active plugins against this report", or any time the user pairs an issue description with a plugin list and wants you to localize the conflict. This skill orchestrates pairwise comparisons via the `find-conflicts` sibling skill — invoke that for each prioritized pair rather than re-implementing its strategy.

Full onboarding for wp-hooks-graph — installs Node dependencies, wires the `hooksgraph` shell alias into the user's RC file, and registers the hooks-graph MCP server with Claude Code. Use whenever the user wants to set up / install / onboard / configure wp-hooks-graph or the hooks-graph MCP server, including phrases like "set this up", "how do I get started", "install hooksgraph", "register the MCP", "wire up the tool", or lands in this repo fresh and asks how to run it. Also use when the user says something broke in their setup and they want it re-run — the skill is idempotent.