custom-jira-context-fetching

Fetches Jira issue summaries, comments, and branch context using jira-cli.

1|Updated Apr 3, 2021
One-click install
npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill custom-jira-context-fetching-naoyamiyagawa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: custom-jira-context-fetching
Source: https://github.com/NaoyaMiyagawa/dotfiles/tree/main/.ai/skills/custom-jira-context-fetching
Command: npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill custom-jira-context-fetching-naoyamiyagawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a user shares a Jira ticket URL or issue key, the assistant lacks the ticket's actual content. This Skill retrieves the issue summary, description, acceptance criteria, and recent comments via the installed jira-cli so implementation guidance and branch naming are grounded in real ticket data. ## Core Features & Use Cases - Issue Key Extraction: Parses issue keys like PN-3429 from Jira URLs using a strict pattern, and asks the user when parsing fails instead of guessing. - Ticket Context Retrieval: Runs jira issue view with optional recent comments or raw structured output to capture summary, acceptance criteria, constraints, and linked work. - Branch Naming Context: Derives branch name suggestions from the issue key and summary, preferring the repository's existing naming convention when visible. - Use Case: A user pastes a Jira URL and asks what the ticket is about; the Skill fetches the ticket, summarizes the description and recent comments, and confirms the parsed key matches. ## Quick Start Fetch and summarize the Jira ticket from this URL and suggest a branch name based on its summary.

Frequently Asked Questions about custom-jira-context-fetching

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

FAQPage Schema
How do I fetch a Jira ticket from the command line?

Run jira issue view followed by the issue key, such as jira issue view PN-3429, using the jira-cli tool. Add --comments 5 to include recent comments, or use jira issue list with a JQL query for raw structured output.

How to extract a Jira issue key from a URL?

Match the URL against the pattern [A-Z][A-Z0-9]+-[0-9]+ to find keys like PN-3429. If no key matches the pattern, ask the user for the exact issue key rather than guessing.

Does jira-cli require setup before fetching issues?

Yes, jira-cli must be installed and configured with your Jira instance credentials before use. Follow the jira-cli getting started guide on GitHub; if authentication or configuration fails, the fetch reports the error and stops.

Can jira-cli generate branch names automatically?

No, jira-cli does not generate branch names by itself. Branch suggestions are derived from the issue key and summary, preferring the repository's existing naming convention visible in git history, with a KEY-short-summary slug as a stated fallback.

When should I skip fetching Jira ticket context?

Skip fetching when the user has already pasted the relevant ticket details into the chat. The fetch only runs when ticket context is actually needed and not already available in the conversation.