jira-auto-detector

# Jira Issue Auto-Detector Skill

You have access to a skill that seamlessly integrates Jira issue context into conversations without polluting the main context window.

## Mission

Enhance user conversations by:
1. **Detecting** Jira issue mentions in user messages
2. **Evaluating** whether issue context is genuinely needed
3. **Fetching** concise summaries via context-isolated subagent
4. **Integrating** information naturally into your response

## Pattern Recognition

### Detect these Jira patterns:

**Issue Keys:**
- Format: `[A-Z]{2,10}-\d{1,6}`
- Examples: EC-1234, IS-8046, PROJ-567
- Common in: "Look at EC-1234", "Implement IS-8046"

**URLs:**
- Format: `https://productboard.atlassian.net/browse/[KEY]`
- Example: "Check https://productboard.atlassian.net/browse/EC-1234"

**Multiple mentions:**
- "Compare EC-1234 and IS-8046"
- "Fixed in EC-1234, EC-1235, IS-8046"

## Intelligence: When to Fetch

### ✅ FETCH when user needs context:

**Direct questions:**
- "What is EC-1234 about?"
- "Tell me about IS-8046"
- "Explain PROJ-567"

**Analysis requests:**
- "Analyze EC-1234"
- "Investigate IS-8046"
- "Review PROJ-567"

**Implementation requests:**
- "Implement EC-1234"
- "Fix IS-8046"
- "Work on PROJ-567"

**Problem-solving:**
- "How should I approach EC-1234?"
- "What's the best solution for IS-8046?"
- "Help me with PROJ-567"

**Comparisons:**
- "Compare EC-1234 and IS-8046"
- "Which is more urgent, EC-1234 or PROJ-567?"

### ❌ DON'T FETCH when context not needed:

**Past tense (already done):**
- "I fixed EC-1234 yesterday"
- "EC-1234 was released last week"
- "Completed IS-8046 this morning"

**Passive listing:**
- "Released with EC-1234, EC-1235, IS-8046"
- "Sprint includes EC-1234 through EC-1240"
- "Changelog: EC-1234, EC-1235"

**Technical identifiers:**
- "The EC-1234 endpoint returns JSON"
- "Call the IS-8046 service"
- "Database table PROJ_567_users"

**Casual reference:**
- "Similar to EC-1234 but different"
- "Reminds me of IS-8046"
- "Like we did in