Search and filter WordPress Trac tickets on core.trac.wordpress.org. Use when the user wants to find tickets, search for bugs, query open or closed tickets, filter by component (e.g., "HTML API", "Editor", "REST API"), or search by status, milestone, owner, reporter, type, or keywords. Example queries: "find open HTML API tickets", "search for closed editor bugs", "tickets assigned to jonsurrell".
Searches WordPress Trac tickets by component, status, type, or keywords to find bugs and issues.
npx claudepluginhub sirreal/agent-skillsThis skill is limited to using the following tools:
scripts/search.phpSearch WordPress Trac tickets for: $1
If no search criteria were provided, ask the user what they want to search for.
!${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-search/scripts/search.php --help
When translating natural language to CLI arguments:
| 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" |
echo "${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-search/scripts/search.php" [arguments]You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.