jira

View Jira issues, generate branches, create tickets, and transition status via Atlassian MCP.

189|25|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-harness --skill jira-sd0xdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/sd0xdev/sd0x-harness/tree/main/skills/jira
Command: npx skills add https://github.com/sd0xdev/sd0x-harness --skill jira-sd0xdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It removes the context-switching between your editor and Jira by letting you view issues, create branches from tickets, transition statuses, and create new tickets directly through the Atlassian MCP integration. ## Core Features & Use Cases - Issue Viewing: Fetch and format Jira issue details (status, assignee, priority, description) from a bare key like OK-51513 or a full Atlassian URL. - Branch Generation: Map issue types to branch prefixes (Bug → fix, Story → feat), generate slugs from summaries, and detect local/remote branch collisions before creating the branch. - Status Transitions & Ticket Creation: Match workflow events (start_work, pr_opened, pr_merged) to available Jira transitions, and create new tickets with markdown descriptions validated against project issue types. - Use Case: You are assigned ticket OK-51513. Run the branch subcommand to get feat/OK-51513-add-user-profile-page, then transition the ticket to In Progress with a single event command when you start work. ## Quick Start Ask the assistant to view Jira ticket OK-51513 and create a branch for it using the jira skill.

Frequently Asked Questions about jira

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a git branch from a Jira ticket?▼

Provide the issue key (e.g., OK-51513) to the branch subcommand. It fetches the issue type and summary, maps the type to a prefix like feat or fix, generates a slug, and outputs or executes git checkout -b with collision detection.

How do I transition a Jira issue status from the command line?▼

Use the transition subcommand with an event such as start_work, pr_opened, or pr_merged. The skill fetches available transitions, matches the target status with regex patterns, and executes the transition after confirmation.

Can I create Jira tickets with markdown descriptions?▼

Yes, the create subcommand sends descriptions with contentFormat set to markdown, supporting headings, lists, bold, code blocks, and links. The issue type is validated at runtime against the project's available types via metadata lookup.

What happens when multiple Atlassian instances are available?▼

The skill resolves the cloudId at runtime by listing accessible resources. If multiple instances exist, it matches the host from the URL or prompts you to choose; it never persists the cloudId between sessions.

When should I not use the Jira skill?▼

Do not use it for GitHub issues, which are handled by the issue-analyze skill, or for generic Jira JQL searching, which is deferred to a later version. It also cannot help with non-Jira project management tools.