linear-issue

Fetches and analyzes Linear issues with comments, attachments, and related GitHub context.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Uguryldz/n8nclean --skill linear-issue-uguryldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linear-issue
Source: https://github.com/Uguryldz/n8nclean/tree/main/.claude/plugins/n8n/skills/linear-issue
Command: npx skills add https://github.com/Uguryldz/n8nclean --skill linear-issue-uguryldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting work on a Linear ticket requires manually gathering scattered context: issue details, comments, screenshots, Loom videos, linked GitHub PRs, and Notion docs. This Skill automates that context-gathering so engineers can begin work with a complete picture. ## Core Features & Use Cases - Full Issue Retrieval: Fetches the Linear issue, its relations, and all comments via the Linear MCP integration. - Media Analysis: Downloads and inspects every screenshot and fetches transcripts for all Loom videos found in the description and comments. - Security Guardrail: Detects n8n-private labeled issues and blocks work when remotes point to the public n8n repository. - Triage Metadata: Identifies the affected n8n node with its popularity score and produces a T-shirt size effort estimate. - Use Case: An engineer assigned ticket AI-1975 runs the Skill to get a summary covering the issue description, all visual evidence, linked PRs, node popularity, and a suggested next-step plan. ## Quick Start Analyze Linear issue AI-1975 and give me a full summary with effort estimate.

Frequently Asked Questions about linear-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a Linear issue before starting work on it?▼

Provide the issue ID such as AI-1975, node-1975, or just the number. The Skill fetches the issue, comments, relations, attachments, and linked GitHub or Notion resources, then returns a structured summary with an effort estimate.

What tools are required to fetch Linear issue context?▼

The Linear MCP server and an authenticated GitHub CLI are required. Notion MCP, the loom-transcript skill, and curl are optional; the Skill degrades gracefully and notes any links you must check manually.

Does the Skill handle private or security-related Linear issues?▼

Yes. It checks for the n8n-private label and inspects git remotes. If any remote points to the public n8n-io/n8n repository, it stops and instructs you to work in a clean clone of the private repository.

How is the effort estimate for a Linear issue determined?▼

It first looks for an estimate from the Flaky auto-triage comment on the issue. If none exists, it assesses scope, complexity, testing, risk, dependencies, and documentation needs, then assigns a T-shirt size from XS to XL.

Can the Skill identify which n8n node an issue affects?▼

Yes. It infers the node from the title, description, labels, and screenshots, resolves the node type ID via node-popularity.json, and reports a popularity score classified as high, medium, or low.