mb-ai-tools

Manage JIRA tickets using the Atlassian MCP tools (preferred) or Atlassian CLI (acli) as fallback. Use when the user asks to view, edit, comment on, create, search, or transition JIRA tickets. Handles authentication, field discovery, custom fields (team, sprint), and output formatting.

CARS project-specific configuration for the carscommerce.atlassian.net org. Activated automatically by /jira-create when the user is working in the CARS project. Provides work hierarchy, issue type names, team field setup, and UUID resolution instructions specific to carscommerce.

Create a well-structured Jira Bug with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions, optional codebase investigation, and MCP-based ticket creation.

Create a well-structured Jira Epic with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions, optional codebase investigation, and MCP-based ticket creation.

Create a well-structured Jira Initiative with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions and MCP-based ticket creation.

Create a well-structured Jira Objective with S.M.A.R.T criteria, key results, and milestones. Invoked internally by the /jira-create command. Objectives are the highest level of the work hierarchy, sitting above Initiatives, Epics, and Stories.

Create a well-structured Jira Story with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions, optional codebase investigation, and MCP-based ticket creation.

Remove signs of AI-generated writing from text to make it sound more natural and human-written. Invoked internally by the /jira-create command to improve tone and clarity of Jira ticket content. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

Ensures git push and PR operations target the correct branch and don't push to merged/closed PRs. Use before any git push, PR creation, or when working across multiple commits in a session.

Create a pull request with consistent formatting, branch naming, and Jira integration. Use when the user asks to create a PR, push and open a PR, or submit their changes for review. Handles branch naming, PR title, description, and respects repo-specific templates.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans. Creates isolated git worktrees with smart directory selection and safety verification.