jira

Fetch Jira issue details via REST API when issue keys are mentioned.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/resolve-io/_prism --skill jira-resolve-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/resolve-io/_prism/tree/main/skills/jira
Command: npx skills add https://github.com/resolve-io/_prism --skill jira-resolve-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a read-only Jira integration to fetch issue context (Epics, Stories, Bugs) directly within your conversation, saving time on context switching and manual lookups.

Core Features & Use Cases

  • Automatic Detection: Recognizes Jira issue keys mentioned in chat (e.g., PLAT-123) and fetches context.
  • Context Fetching: Retrieves full issue details via Jira REST API.
  • Structured Formatting: Presents data in a clear, developer-friendly format.
  • Linked Issues & Hierarchy: Follows Epic → Story → Task relationships for full traceability.
  • Comments & Acceptance Criteria: Shows recent comments and extracts AC from description or custom fields.
  • Graceful Degradation: Continues without Jira if the API is unavailable or rate-limited.

Quick Start

Try: "jira PLAT-123" to fetch issue details, or enable automatic detection with "auto-detect on" and let the skill pull context when you mention a Jira key.

Frequently Asked Questions about jira

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

FAQPage Schema
How do I fetch Jira issue context automatically when working in chat?

Fetching Jira issue context automatically works by recognizing Jira issue keys (e.g., PLAT-123) mentioned in conversation and retrieving full details via the Jira REST API. Enable automatic detection with "auto-detect on" to pull issue context without explicit commands, saving context-switching time during development workflows.

What Jira issue information can I retrieve through the REST API integration?

The REST API integration retrieves full issue details including acceptance criteria, recent comments, linked issues, and Epic→Story→Task hierarchy relationships. Data is presented in structured, developer-friendly format to support traceability and reduce manual lookups across your issue tracking system.

Do I need special authentication setup to read Jira issues in chat?

Authentication requires Jira credentials stored in environment variables. The Skill enforces read-only access, handles credentials securely, implements session caching, and degrades gracefully if the API is unavailable or rate-limited, so you maintain secure, reliable access without manual credential management.

Can I use this Jira integration if my team uses read-only access controls?

Yes, this Skill is designed specifically for read-only Jira access. It enforces read-only permissions by default, meaning it fetches and displays issue context without write capabilities, making it safe for teams with restricted access policies or CI/CD workflows requiring minimal permissions.

How does the Skill handle Jira API rate limits and downtime?

The Skill implements graceful degradation, rate-limiting handling, and session caching to continue functioning when the Jira REST API is unavailable or rate-limited. This ensures conversations proceed without blocking on transient API issues while maintaining secure, efficient credential handling.

What format does the Skill use to present linked Jira issues and hierarchies?

Linked issues and hierarchies are presented in structured format following Epic→Story→Task relationships. The Skill formats acceptance criteria, comments, and issue dependencies in a clear, developer-friendly layout to support full traceability and reduce context-switching during development.