How this command is triggered — by the user, by Claude, or both
Slash command
/wp-dev:wp-hooks-refThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /wp-hooks-ref Look up WordPress and WooCommerce hooks by name or topic. ## Instructions Load the `wp-hooks` skill for hook documentation methodology. The user provides a hook name, partial name, or topic after `/wp-hooks-ref`. For example: - `/wp-hooks-ref save_post` — Show the `save_post` hook details - `/wp-hooks-ref woocommerce_checkout` — List hooks matching "woocommerce_checkout" - `/wp-hooks-ref auth` — Search for authentication-related hooks ### Behavior 1. **Exact match**: If the argument matches a known hook name exactly, provide: - Hook type (action or filter) - Func...
Look up WordPress and WooCommerce hooks by name or topic.
Load the wp-hooks skill for hook documentation methodology.
The user provides a hook name, partial name, or topic after /wp-hooks-ref. For example:
/wp-hooks-ref save_post — Show the save_post hook details/wp-hooks-ref woocommerce_checkout — List hooks matching "woocommerce_checkout"/wp-hooks-ref auth — Search for authentication-related hooksExact match: If the argument matches a known hook name exactly, provide:
Partial match / prefix: If the argument is a prefix (e.g., woocommerce_), list all matching hooks from the plugin's reference files, grouped by category.
Topic search: If the argument is a general topic (e.g., "auth", "login", "media"), search for related hooks and present them organized by relevance.
First check the plugin's built-in references:
skills/woocommerce/references/woo-hooks.md for WooCommerce hooksskills/wordpress-patterns/SKILL.md for common WordPress patternsFor hooks not covered in the local references, use your built-in knowledge of the WordPress hook system. Only use WebSearch as a last resort for very specific or rarely-used hooks.
For each hook, provide:
## hook_name (action|filter)
**Signature:** `do_action( 'hook_name', $param1, $param2 )` or `apply_filters( 'hook_name', $value, $context )`
**Parameters:**
- `$param1` (type) — Description
- `$param2` (type) — Description
**Fires:** Description of when this hook fires.
**Example:**
\`\`\`php
add_action( 'hook_name', function ( $param1, $param2 ): void {
// Usage example
}, 10, 2 );
\`\`\`
**Related:** `other_hook`, `another_hook`
If no arguments are provided, ask the user what hook they want to look up.
npx claudepluginhub iwritec0de/claude-plugin-marketplace --plugin wp-dev