sirreal/wp-trac-ticket
plugins/wordpress-trac/skills/wp-trac-ticket/SKILL.md
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
Updated May 15, 2026
$ install --global
skillsauthnpx skillsauth add sirreal/agent-skills wp-trac-ticketInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 4:36 AM10.5s3 files scanned
SKILL.md
- name:
- wp-trac-ticket
- description:
- >-
- information about it:
- metadata, description, attachments, linked
- #62345, 62345, or https:
- //core.trac.wordpress.org/ticket/62345. Use
- - Bash(${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-ticket/scripts/ticket.php:
- *)
- argument-hint:
- [--short] <ticket-number>
Look up WordPress Trac ticket information.
If no ticket number was provided, ask the user which ticket they want to look up.
Input formats
Pass the numeric ticket number to the script (e.g. 30000). The script
also accepts #30000 or a full ticket URL.
Choosing a mode
The default mode returns everything: metadata, description, attachments,
changesets, comments, and pull requests. Use --short only when the user
wants a quick metadata-only glance (no comments/attachments/changesets/PRs).
| User says | Mode |
|-----------|------|
| "look up ticket 30000" | default |
| "show me ticket #62345" | default |
| "what's the discussion on ticket 50000" | default |
| "what PRs are open for #62345" | default |
| "quick status check on ticket 12345" | --short |
| "just the metadata for #30000" | --short |
Commands
- Full: !
echo "${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-ticket/scripts/ticket.php"<ticket-number> - Short: !
echo "${CLAUDE_PLUGIN_ROOT}/skills/wp-trac-ticket/scripts/ticket.php"--short <ticket-number>
Output
Both modes start with a metadata header (component, summary, reporter, owner, type, status, resolution, priority, severity, version, milestone, keywords, focuses; empty fields are suppressed) followed by the description.
The default mode then appends, in order:
- Attachments: each attached file with uploader, date, and a direct URL.
- Changesets: each Trac changeset that referenced the ticket via an
In [N]:auto-comment, with committer, date, URL, and commit message. - Discussion: each comment with author, comment number, date, any inline field-change context (status / owner / milestone / resolution changes — keyword churn is intentionally dropped), and body.
- Pull Requests: GitHub PRs linked to the ticket, sorted open-first then by most-recent update. Each shows number, title, state, author, URL, created/updated/closed dates, +/− line counts, whether tests are touched, CI status, and reviewer status.
Related Skills
sirreal/wp-trac-fix
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 15, 2026
sirreal/wp-trac-timeline
testing
VerifiedTrustedCommunity
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".
SKILL.mdUpdated May 14, 2026
sirreal/wp-trac-search
development
VerifiedTrustedCommunity
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>".
SKILL.mdUpdated May 9, 2026
sirreal/wp-trac-changeset
tools
VerifiedTrustedCommunity
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".
SKILL.mdUpdated May 9, 2026