read-jira

Fetch Jira issue details from a URL or key.

Updated Apr 6, 2026

Search Tags:#planning #integration #fetch #comments #jira #issue #subtasks

Ready to run

npx skills add https://github.com/son-nguyen-301/hydra-claude --skill read-jira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: read-jira
Source: https://github.com/son-nguyen-301/hydra-claude/tree/main/skills/read-jira
Command: npx skills add https://github.com/son-nguyen-301/hydra-claude --skill read-jira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a Jira ticket URL or key is provided, fetch and load its content into the planning context to keep stakeholders aligned and reduce manual data gathering.

Core Features & Use Cases

Fetch Jira issue by URL or key, extracting Title, Description, Status, Assignee, and Reporter.
Retrieve Comments, Subtasks, Parent, and Linked Issues to provide full context for planning and execution.
Use Case: A product team pastes a Jira URL into the chat to load ticket details for planning, estimation, and task breakdown.

Quick Start

Paste a Jira ticket URL to fetch its content and load it into the planning context.

Frequently Asked Questions about read-jira

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

FAQPage Schema

How do I fetch Jira issue details like description and status from a ticket URL?▼

To fetch Jira issue details, provide a Jira ticket URL or key. The tool automatically retrieves the title, status, description, assignee, and reporter for immediate team alignment during planning and status reviews.

Can I retrieve Jira subtasks and linked issues for requirement mapping?▼

Yes, you can retrieve Jira subtasks and linked issues. Providing a Jira issue key loads parent tickets, linked issues, and comments to provide full context for requirement mapping and task breakdown.

Does fetching Jira comments work for pasting ticket content into team planning?▼

Fetching Jira comments works for team planning by loading inline ticket data into the context. It extracts comments and subtasks when a Jira URL is provided, reducing manual data gathering for estimations.

What is the best way to load Jira ticket content for sprint planning and estimation?▼

The best way to load Jira ticket content for sprint planning is pasting the ticket URL. This automatically fetches description, assignee, and subtasks, keeping stakeholders aligned without manual data entry.

Do I need a specific Jira URL format to extract ticket title and assignee?▼

You need a standard Jira URL or issue key to extract the ticket title and assignee. The system automatically parses the provided identifier to load the relevant issue content into your planning context.