Search WordPress Trac tickets for: $1

Script documentation:

Search will be performed by using a command line script. The script MUST BE invoked directly as ${CLAUDE_PLUGIN_ROOT}/skills/search/scripts/search.php. NEVER use php to call the script.

Script documentation guide

!${CLAUDE_PLUGIN_ROOT}/skills/search/scripts/search.php --help

Translation Guide

When translating natural language to CLI arguments:

"open tickets" → --status=new --status=assigned --status=accepted --status=reopened --status=reviewing
"closed tickets" → --status=closed
Only use --component when there's a very obvious match to an exact component name (e.g., "HTML API", "REST API")
When in doubt, use --summary and --description text search instead of --component
Use --summary for text search in ticket title
Use --description for text search in ticket body

Examples

User request	CLI arguments
"open HTML API tickets"	--component="HTML API" --status=new --status=assigned --status=accepted --status=reopened --status=reviewing
"closed REST API bugs"	--component="REST API" --status=closed --type="defect (bug)"
"tickets about block editor"	--summary="block editor" --description="block editor"

Instructions

Parse the user's description to identify filters and search terms
Build the correct CLI arguments using the documented options
Run: ${CLAUDE_PLUGIN_ROOT}/skills/search/scripts/search.php [arguments]
Review results - it's expected to try several different queries to find good results
Try different combinations: broader/narrower searches, different text terms, with/without component filters
Return the final results