skills/sirreal/agent-skills/wp-trac-search

wp-trac-search

SKILL.md

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

  1. Parse the user's description to identify filters and search terms
  2. Build the correct CLI arguments using the documented options
  3. Run: !echo "${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-search/scripts/search.php" [arguments]
  4. Review results — try several different queries to find good results
  5. Try different combinations: broader/narrower searches, different text terms, with/without component filters
  6. Return the final results
Weekly Installs
4
First Seen
Feb 12, 2026
Installed on
amp4
gemini-cli4
claude-code4
github-copilot4
codex4
kimi-cli4