// Fetch and display a Jira ticket's description, comments, attachments, and linked tickets
Use when reviewing tests or test changes in a diff, pull request, or merge request. Triggers on assessing test quality, spotting test anti-patterns, or evaluating whether an assertion earns its place.
Generate the periodic "unsolved Checkmk check crashes on 2.4+" Slack rollup, grouped by component owner. Composes the crash-report and component-owners skills and emits Slack-ready plain text (no markdown).
Queries and reads crash reports from crash.checkmk.com
Create a Jira ticket in CMK with component, team, and epic matched from compass and roadmap data
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Interacts with Gerrit code review to list changes and improve them
| name | jira-read-ticket |
| description | Fetch and display a Jira ticket's description, comments, attachments, and linked tickets |
Fetches a Jira ticket and displays its full context: description, comments, attachments, and linked tickets. User names are anonymized.
Note: This skill is limited to the CMK project to avoid interfering with sensitive customer data. Only
CMK-prefixed tickets are supported.
The user provides one or more Jira ticket keys as the argument (e.g., /jira-read-ticket CMK-12345 or /jira-read-ticket CMK-12345 CMK-67890).
For each ticket key provided, run the helper script:
.venv/bin/python .github/skills/jira-read-ticket/read_ticket.py <TICKET_KEY>
If the script fails, report the error to the user and continue with the remaining tickets.
If multiple tickets are requested, fetch them in parallel using separate Bash calls.
Skip this step entirely if the script output contains no attachment sections.
If there are attachments, launch at most 2 Task agents (subagent_type: general-purpose) in parallel:
Present the ticket context to the user. Summarize the key information:
Keep it concise — the user can ask follow-up questions if they need more detail.