Authenticate to WordPress Trac by capturing the browser session cookie so the other wp-trac skills can fetch filtered data. Use when a Trac request reports "auth required", when the cookie is missing or expired, or when the user asks to log in to / authenticate with Trac. Walks the user through copying the Cookie: header and persists it securely.
Look up a WordPress Trac changeset (commit, revision) to see the commit message, author, and timestamp. Accepts [41062], r41062, or https://core.trac.wordpress.org/changeset/41062. Use when the user asks about a commit, revision, changeset, or "what changed in rNNNNN".
Search and filter WordPress Trac tickets on core.trac.wordpress.org. Use when the user wants to find tickets matching criteria, 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. NOT for looking up a single ticket by number — use wp-trac-ticket for that. Example queries: "find open HTML API tickets", "search for closed editor bugs", "tickets assigned to <username>".
Look up a specific WordPress Trac ticket by its number to see all information about it: metadata, description, attachments, linked changesets, discussion comments, and GitHub pull requests. Accepts #62345, 62345, or https://core.trac.wordpress.org/ticket/62345. Use whenever the user references a specific ticket number. Do NOT use wp-trac-search for single ticket lookups.
Browse WordPress Trac timeline activity feed. Use when the user asks about recent WordPress core Trac activity, commits, ticket changes, or what a specific author has been working on. Matches queries like "recent trac activity", "what has USER done on trac", "WordPress core commits this week", "show me USER's trac contributions".
Reproduce and attempt a fix for a specific WordPress core defect from Trac in an isolated worktree. Use when the user asks to "work on Trac #N", "fix Trac ticket #N", "reproduce and fix #N", or similar.