What problem does it solve? Working the MariaDB documentation Jira project by hand means juggling ticket transitions, feature branches, PR links, and reviewer follow-ups across Jira, Git, and Slack. This Skill centralizes that plumbing so every Jira workflow command shares one verified connection check, project configuration, and set of transition rules. ## Core Features & Use Cases - Ticket lifecycle management: Start work on a DOCS ticket (assign, cut a feature branch, move to In Progress), create new Tasks or Epics, hand off to Review with the PR link and fact-check report, and close after merge. - Ticket listing and commenting: List your open assigned DOCS tickets via JQL and post Markdown-formatted comments on any ticket. - Reviewer chasing: Identify reviewers of tickets waiting in Review, detect who has already replied, and draft Slack DM nudges that are always confirmed before sending. - Use Case: You are asked to start DOCS-1234. The Skill verifies the Atlassian connection reaches mariadbcorp, fetches the ticket, assigns it to you, creates the branch DOCS-1234-short-slug from latest main, and transitions the ticket to In Progress. ## Quick Start Ask the assistant to start work on DOCS-1234 and it will verify the Jira connection, create the feature branch, and move the ticket to In Progress.
