jira-ticket-reader

Read Jira ticket data from the current git branch and generate Markdown task documentation.

1|Updated Feb 11, 2019
One-click install
npx skills add https://github.com/ddieppa/dotfiles --skill jira-ticket-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-ticket-reader
Source: https://github.com/ddieppa/dotfiles/tree/main/.agents/skills/jira-ticket-reader
Command: npx skills add https://github.com/ddieppa/dotfiles --skill jira-ticket-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Read Jira tickets and create a task folder with ticket information and a starting prompt, streamlining context creation for development tasks.

Core Features & Use Cases

  • Extracts ticket data from the current branch and fetches complete Jira issue details.
  • Generates Markdown documentation and a ready-to-use starting prompt for AI-assisted development.
  • Organizes outputs into a predictable folder structure for quick onboarding.

Quick Start

Instruct the AI assistant to read the ticket details from your current branch and generate the task documentation and prompt.

Frequently Asked Questions about jira-ticket-reader

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

FAQPage Schema
How do I automatically generate task documentation from a Jira ticket?

To automatically generate task documentation from a Jira ticket, this Skill reads ticket data directly from your current git branch and outputs Markdown artifacts containing ticket details and a starting prompt.

What do I need to extract Jira issue details from my git branch?

You need Jira access and proper branch naming to extract Jira issue details from your git branch. The Skill uses these prerequisites to fetch complete ticket data and generate documentation.

Can I create AI-assisted development prompts directly from Jira tickets?

Yes, you can create AI-assisted development prompts directly from Jira tickets. The Skill generates a ready-to-use starting prompt alongside Markdown documentation to streamline context creation.

How does branch naming affect Jira ticket data extraction?

Branch naming affects Jira ticket data extraction because the Skill parses the current git branch name to identify the ticket ID. Proper branch naming is required to successfully fetch the corresponding Jira issue details.

Where are generated Markdown task docs stored when reading Jira tickets?

Generated Markdown task docs are stored under the personal/tasks folder. The Skill creates predictable folder structures containing ticket information, a starting prompt, and a link to the Jira issue.

What is the best way to capture Jira ticket context for development workflows?

The best way to capture Jira ticket context for development workflows is to automatically extract ticket data from your current branch and generate structured Markdown artifacts for quick onboarding and knowledge transfer.