Does this skill fetch every Jira key I mention in the chat?

No, it uses intelligent pattern recognition to only fetch context when it determines the information is needed for analysis, implementation, or problem-solving, avoiding unnecessary API calls for casual mentions.

Does it remember issues I've already fetched?

Yes, it maintains session memory to track previously fetched issue keys, allowing it to reuse existing summaries and provide faster responses within the same conversation.

Can I compare multiple Jira issues at once?

Yes, the skill can handle multiple mentions and sequentially fetch summaries for up to three issues at a time to help with comparison and technical planning.

What happens if a Jira issue cannot be found?

The skill includes built-in error handling that will gracefully inform you if an issue is inaccessible or non-existent, allowing you to provide manual context or verify the ID.

Will fetching large Jira tickets fill up my conversation context?

The skill uses a 'jira-analyzer' subagent that processes the full ticket data in an isolated window and returns only a concise 800-token summary to your main session, preserving your context for code.

Jira Issue Auto-Detector

Name: Jira Issue Auto-Detector
Author: schovi

byschovi

コラボレーションツール

Automatically identifies Jira issue references and intelligently retrieves relevant context to streamline project management and development workflows.

概要

The Jira Issue Auto-Detector skill enhances your Claude Code environment by seamlessly integrating project context without manual data entry. It scans your conversation for Jira issue keys and URLs, then uses specialized logic to determine if detailed context is required for the task at hand. By delegating the heavy lifting to an isolated subagent, it fetches concise, high-value summaries of tickets—including status, priority, and acceptance criteria—while keeping your main context window clean and focused on code implementation.

主な機能

Context-isolated fetching via jira-analyzer subagent to prevent token pollution
Session-based memory to prevent redundant fetches and save API overhead
0 GitHub stars
Automatic detection of Jira issue keys and Atlassian URLs
Intelligent context evaluation to skip fetching for passing mentions or past-tense references
Seamless integration of ticket summaries including description and acceptance criteria

ユースケース

Comparing multiple Jira issues to determine technical approaches or priorities
Summarizing complex requirements for technical analysis within the CLI
Implementing features or bug fixes directly from a Jira ticket reference

概要

主な機能

Context-isolated fetching via jira-analyzer subagent to prevent token pollution
Session-based memory to prevent redundant fetches and save API overhead
0 GitHub stars
Automatic detection of Jira issue keys and Atlassian URLs
Intelligent context evaluation to skip fetching for passing mentions or past-tense references
Seamless integration of ticket summaries including description and acceptance criteria

ユースケース

Comparing multiple Jira issues to determine technical approaches or priorities
Summarizing complex requirements for technical analysis within the CLI
Implementing features or bug fixes directly from a Jira ticket reference