linear-awareness

# Linear Skills Guide

You have specialized Linear issue management skills. Use these for structured ticket workflows during debugging investigations.

## Decision Tree

### Skills vs Agents

**Simple issue fetch or update?**
→ Use Linear skills
- `linear-issues` - Fetch, list, search issues (single linearis command)
- `linear-update` - Update issue, add comments
- Example: "Get details for ENG-1234"
- Use when: Single issue, straightforward query/update

**Complex investigation requiring analysis?**
→ Use Task tool with Linear agents (conserves context)
- `linear-locator` - Find issues by criteria, save to /tmp
- `linear-analyzer` - Extract debugging context, parse technical details
- `linear-pattern-finder` - Find patterns across issues, detect recurring problems
- Use when: Multi-issue analysis, pattern detection, trend analysis

### When to Use Which Agent

**Just need to find issues broadly?**
→ Use `linear-locator` agent only
- Lists/searches issues by team, label, state, text
- Saves filtered results to /tmp
- Example: "Find all FileB-related issues across teams"

**Investigating single issue for debugging?**
→ Use `linear-locator` + `linear-analyzer` agents
- Locator: Find issue and related issues
- Analyzer: Extract error messages, URLs, technical details
- Example: "Analyze ENG-1234 for debugging context"

**Need to find patterns or recurring problems?**
→ Use all three: `linear-locator` + `linear-analyzer` + `linear-pattern-finder`
- Locator: Fetch issues by criteria
- Analyzer: Parse each issue for technical details
- Pattern-finder: Correlate across issues, find recurring themes, temporal trends
- Example: "Find recurring VCS permission errors across last 2 months"

**Adding debugging findings to a ticket?**
→ Use `linear-update` skill
- Better than: Running raw `linearis comments create` commands
- Example: "Add root cause analysis to ENG-1234"

**Updating issue status after investigation?**
→ Use `linear-update` skill
- Includes: status, priority, lab