wp-trac-search | wordpress-trac | ClaudePluginHub

Skill

Community

wp-trac-search

From wordpress-trac

0

Description

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".

AI Summary

Searches WordPress Trac tickets by component, status, type, or keywords to find bugs and issues.

Install

1

Run in your terminal

$

npx claudepluginhub sirreal/agent-skills

Tool Access

This skill is limited to using the following tools:

Bash(${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-search/scripts/search.php:*)

Supporting Assets

View in Repository

scripts/search.php

Skill Content

Search WordPress Trac tickets for: $1

If no search criteria were provided, ask the user what they want to search for.

Script reference

!${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-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: !echo "${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-search/scripts/search.php" [arguments]
Review results — 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

Links

GitHub Stats

0 forks

Updated 10 days ago

Actions

Similar Skills

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.

68.7k

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

68.7k

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

68.7k