plugins/wordpress-trac/skills/wp-trac-timeline/SKILL.md
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".
npx skillsauth add sirreal/agent-skills wp-trac-timelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query WordPress Trac timeline for: $1
!${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-timeline/scripts/timeline.php --help
Today's date is used to calculate dates. Convert relative dates to explicit parameters:
| User says | Calculation |
|-----------|-------------|
| "last 2 weeks" | --daysback=14 |
| "past month" | --daysback=30 |
| "last 7 days" | --daysback=7 |
| "around Jan 12, 2023" | --from=2023-01-15 --daysback=7 (center on the date) |
| "January 2023" | --from=2023-01-31 --daysback=31 |
| "since Feb 1" | Calculate days from Feb 1 to today |
| User request | CLI arguments |
|--------------|---------------|
| "my activity last 2 weeks" | --author=<username> --daysback=14 |
| "what did saxmatt and ryan do in early 2005" | --from=2005-01-15 --daysback=15 --author=saxmatt --author=ryan |
| "all trac activity yesterday" | --daysback=1 |
| "what <username> worked on this month" | --author=<username> --daysback=30 |
--from and --daysback from relative datesecho "${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-timeline/scripts/timeline.php" [arguments]testing
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.
development
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.
development
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>".
tools
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".