// Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
| name | linear-issue |
| description | Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue. |
| disable-model-invocation | true |
| argument-hint | [issue-id] |
| compatibility | {"requires":[{"mcp":"linear","description":"Core dependency — used to fetch issue details, relations, and comments"},{"cli":"gh","description":"GitHub CLI — used to fetch linked PRs and issues. Must be authenticated (gh auth login)"}],"optional":[{"mcp":"notion","description":"Used to fetch linked Notion documents. Skip Notion steps if unavailable."},{"skill":"loom-transcript","description":"Used to fetch Loom video transcripts. Skip Loom steps if unavailable."},{"cli":"curl","description":"Used to download images/attachments. Typically pre-installed."}]} |
Start work on Linear issue $ARGUMENTS
This skill depends on external tools. Before proceeding, verify availability:
Required:
mcp__linear): Must be connected. Without it the skill cannot function at all.gh): Must be installed and authenticated. Run gh auth status to verify. Used to fetch linked PRs and issues.Optional (graceful degradation):
mcp__notion): Needed only if the issue links to Notion docs. If unavailable, note the Notion links in the summary and tell the user to check them manually./loom-transcript): Needed only if the issue contains Loom videos. If unavailable, note the Loom links in the summary for the user to watch.If a required tool is missing, stop and tell the user what needs to be set up before continuing.
Follow these steps to gather comprehensive context about the issue:
Use the Linear MCP tools to fetch the issue details and comments together:
mcp__linear__get_issue with the issue ID to get full details including attachmentsmcp__linear__list_comments with the issue ID to fetch all commentsBoth calls should be made together in the same step to gather the complete context upfront.
IMPORTANT: This step is NOT optional. You MUST scan and fetch all visual content from BOTH the issue description AND all comments.
Screenshots/Images (ALWAYS fetch):
<img> tagscurl -sL "url" -o /path/to/image.png (GitHub URLs require following redirects) OR the linear mcpRead tool on the downloaded file to view itLoom Videos (ALWAYS fetch transcript):
/loom-transcript skill to fetch the FULL transcriptRelated Linear Issues:
mcp__linear__get_issue for any issues mentioned in relations (blocking, blocked by, related, duplicates)GitHub PRs and Issues:
gh CLI to fetch PR/issue details:
gh pr view <number> for pull requestsgh issue view <number> for issuescurl -H "Authorization: token $(gh auth token)" -L <image-url> -o image.pngNotion Documents:
mcp__notion__notion-fetch with the Notion URL or page ID to retrieve document contentComments were already fetched in Step 1. Review them for:
Determine whether this issue is specific to a particular n8n node (e.g. a trigger, action, or tool node). Look for clues in:
node:linear, node:slack)If the issue is node-specific:
Find the node type ID. Use Grep to search for the node's display name (or keywords from it) in packages/frontend/editor-ui/data/node-popularity.json to find the exact node type ID. For reference, common ID patterns are:
n8n-nodes-base.<camelCaseName> (e.g. "HTTP Request" → n8n-nodes-base.httpRequest)n8n-nodes-base.<name>Trigger (e.g. "Gmail Trigger" → n8n-nodes-base.gmailTrigger)n8n-nodes-base.<name>Tool (e.g. "Google Sheets Tool" → n8n-nodes-base.googleSheetsTool)@n8n/n8n-nodes-langchain.<camelCaseName> (e.g. "OpenAI Chat Model" → @n8n/n8n-nodes-langchain.lmChatOpenAi)Look up the node's popularity score from packages/frontend/editor-ui/data/node-popularity.json. Use Grep to search for the node ID in that file. The popularity score is a value between 0 and 1, where 1 means the most popular node. Include this in the summary to help gauge the impact/reach of the issue.
If the node is not found in the popularity file, note that it may be a community node or a very new/niche node.
After gathering all context, assess the effort required to fix/implement the issue. Use the following T-shirt sizes:
| Size | Approximate effort |
|---|---|
| XS | ≤ 1 hour |
| S | ≤ 1 day |
| M | 2-3 days |
| L | 3-5 days |
| XL | ≥ 6 days |
To make this assessment, consider:
Provide the T-shirt size along with a brief justification explaining the key factors that drove the estimate.
Before presenting, verify you have completed:
gh CLIAfter gathering all context, present a comprehensive summary including:
n8n-nodes-base.xxx), and popularity score (e.g. 0.414 — higher means more widely used, so bugs have broader impact)AI-1975, node-1975, or just 1975 (will search)