jira-ticket

Fetch Jira ticket details and map issue types to branch prefixes.

6|Updated Jan 22, 2026

Search Tags:#mcp #jira #ticket #branch #issue #summary #prefix

Ready to run

npx skills add https://github.com/flurdy/agent-skills --skill jira-ticket-flurdy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-ticket
Source: https://github.com/flurdy/agent-skills/tree/main/skills/jira-ticket
Command: npx skills add https://github.com/flurdy/agent-skills --skill jira-ticket-flurdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly retrieve Jira ticket details (key, summary, type, and description) to inform branch naming, PR creation, and requirement understanding.

Core Features & Use Cases

Retrieve Jira ticket details (key, summary, type, description) via the configured MCP Jira server.
Determine a conventional commit prefix based on the issue type (e.g., Story -> feat, Bug -> fix).
Return ticket information suitable for branch naming and PR summaries, including a suggested branch name.

Quick Start

Run /jira-ticket SP-123 to retrieve ticket details and the suggested branch prefix.

Frequently Asked Questions about jira-ticket

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

FAQPage Schema

How do I get Jira ticket details for branch naming?▼

To get Jira ticket details for branch naming, you can use the jira-ticket command to fetch the key, summary, type, and description from the MCP Jira endpoint. It generates a suggested branch name and conventional commit prefix based on the issue type.

Can I generate a git branch name from a Jira issue summary?▼

Yes, you can generate a git branch name from a Jira issue summary. The Skill fetches the ticket summary and issue type via the Jira API, returning a mapped branch prefix and key to construct an appropriate branch name.

How do I map Jira issue types to conventional commit prefixes?▼

You can map Jira issue types to conventional commit prefixes automatically. The Skill determines the prefix based on the fetched issue type, such as mapping a Story to 'feat' or a Bug to 'fix' for your commit messages and PR descriptions.

Does this Jira ticket fetcher work across all Jira projects?▼

Yes, the Jira ticket fetcher works across all Jira projects. It uses the standard /rest/api/3/issue/{ticketNumber} endpoint to retrieve issue fields, making it applicable for generating branch names and PR planning regardless of the specific project.

Do I need an MCP Jira server configured to fetch issue details?▼

Yes, you need an MCP Jira server configured. The Skill relies on the configured MCP Jira endpoint to fetch the necessary ticket fields like key, summary, type, and description to support your branch naming and PR creation workflow.