yellow-linear

Create a Linear issue from current context. Use when user describes a bug, requests a feature, says "file an issue", "track this", or "create ticket for X".

Delegate a Linear issue to a Devin AI session. Use when you want to hand off an issue to Devin for autonomous implementation. Requires Devin credentials (DEVIN_SERVICE_USER_TOKEN, DEVIN_ORG_ID).

Plan sprint cycle by selecting backlog issues. Use when user says "plan the sprint", "fill the cycle", "what should we work on next", or "sprint planning".

Validate Linear MCP availability and first-use OAuth readiness. Use when first installing the plugin, after clearing auth, or when Linear tools stop working.

Generate project and initiative health report. Use when user asks "project status", "how are we tracking", "what's blocked", or "sprint health".

Deep search and analysis of Linear backlog. Use when user asks to search, analyze, or explore Linear issues, projects, or backlog. Also use when user says "search linear", "has anyone reported", "find similar issues", "is this a duplicate", "what's in the backlog", or "related issues".

Auto-load Linear issue context from branch name. Use when user is working on a branch whose name contains a Linear issue identifier (e.g., ENG-123, feat/ENG-123-auth-flow). Also use when user says "load issue", "get context", "what's this issue about", or asks for background on a Linear issue.

Suggest linking pull requests to Linear issues and syncing status. Use when user creates a pull request via gt submit (Graphite) or mentions submitting a PR and the branch name contains a Linear issue identifier. Also use when user says "link to linear", "update issue from PR", or "sync status". IMPORTANT: Always confirm with user before updating Linear issue status.

Linear workflow patterns and conventions reference. Use when commands or agents need Linear workflow context, issue writing guidance, or branch naming conventions.