Add Linear integration skill

[sentry-junior]

Summary

Junior currently supports GitHub issue management as a skill but has no equivalent for Linear. Sentry uses Linear for project/ticket tracking, so team members cannot create or update Linear tickets directly from Slack without context-switching. Adding a Linear skill would close this gap with the same code-informed, provenance-linked workflow available today for GitHub.

Current behavior

No Linear skill exists. Team members must open Linear manually or rely on the native Linear Slack bot, which operates without access to code context, Sentry error data, or thread provenance.

Gap

The native Linear agent can draft tickets but cannot:

• Pull source code or stack traces to ground ticket details
• Reference a Sentry issue or event URL as the trigger
• Preserve the originating Slack thread as provenance on the ticket

The GitHub skill already solves all three for GitHub-tracked work; Linear needs the same treatment.

Options

1. Linear MCP / API skill — implement analogous to the GitHub skill using the Linear GraphQL API directly; supports create, update, comment, and state transitions
2. Linear Slack integration passthrough — lean on existing Linear×Slack automation; lower engineering cost but no code-context or Sentry enrichment
3. Hybrid — use option 1 for junior-initiated tickets; let native Linear bot handle emoji-triggered quick captures

Recommendation

Option 1 (Linear API skill), following the GitHub skill pattern. The highest-value use case is creating well-formed tickets enriched with code context and Sentry data — that requires a direct API integration, not a passthrough.

Action taken on behalf of David Cramer.