Linear Issue Analysis

Start work on Linear issue $ARGUMENTS

Prerequisites

This skill depends on external tools. Before proceeding, verify availability:

Required:

Linear MCP (
```
mcp__linear
```
): Must be connected. Without it the skill cannot function at all.
GitHub CLI (
```
gh
```
): Must be installed and authenticated. Run
```
gh auth status
```
to verify. Used to fetch linked PRs and issues.

Optional (graceful degradation):

Notion MCP (
```
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 skill (
```
/loom-transcript
```
): Needed only if the issue contains Loom videos. If unavailable, note the Loom links in the summary for the user to watch.
curl: Used to download images. Almost always available; if missing, skip image downloads and note it.

If a required tool is missing, stop and tell the user what needs to be set up before continuing.

Instructions

Follow these steps to gather comprehensive context about the issue:

1. Fetch the Issue and Comments from Linear

Use the Linear MCP tools to fetch the issue details and comments together:

Use
```
mcp__linear__get_issue
```
with the issue ID to get full details including attachments
Include relations to see blocking/related/duplicate issues
Immediately after, use
```
mcp__linear__list_comments
```
with the issue ID to fetch all comments

Both calls should be made together in the same step to gather the complete context upfront.

2. Analyze Attachments and Media (MANDATORY)

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):

Scan the issue description AND all comments for ALL image URLs:
- ```
<img>
```
  tags
- Markdown images
```
![](url)
```
- Raw URLs (github.com/user-attachments, imgur.com, etc.)
For EACH image found (in description or comments):
- Download using
```
curl -sL "url" -o /path/to/image.png
```
  (GitHub URLs require following redirects)
- Use the
```
Read
```
  tool on the downloaded file to view it
- Describe what you see in detail
Do NOT skip images - they often contain critical context like error messages, UI states, or configuration

Loom Videos (ALWAYS fetch transcript):

Scan the issue description AND all comments for Loom URLs (loom.com/share/...)
For EACH Loom video found (in description or comments):
- Use the
```
/loom-transcript
```
  skill to fetch the FULL transcript
- Summarize key points, timestamps, and any demonstrated issues
Loom videos often contain crucial reproduction steps and context that text alone cannot convey

3. Fetch Related Context

Related Linear Issues:

Use
```
mcp__linear__get_issue
```
for any issues mentioned in relations (blocking, blocked by, related, duplicates)
Summarize how they relate to the main issue

GitHub PRs and Issues:

If GitHub links are mentioned, use
```
gh
```
CLI to fetch PR/issue details:
- ```
gh pr view <number>
```
  for pull requests
- ```
gh issue view <number>
```
  for issues

Download images attached to issues:

curl -H "Authorization: token $(gh auth token)" -L <image-url> -o image.png

Notion Documents:

If Notion links are present, use
```
mcp__notion__notion-fetch
```
with the Notion URL or page ID to retrieve document content
Summarize relevant documentation

4. Review Comments

Comments were already fetched in Step 1. Review them for:

Additional context and discussion history
Any attachments or media linked in comments (process in Step 2)
Clarifications or updates to the original issue description

5. Present Summary

Before presenting, verify you have completed:

Downloaded and viewed ALL images in the description AND comments
Fetched transcripts for ALL Loom videos in the description AND comments
Fetched ALL linked GitHub issues/PRs via
```
gh
```
CLI
Listed all comments on the issue

After gathering all context, present a comprehensive summary including:

Issue Overview: Title, status, priority, assignee, labels
Description: Full issue description with any clarifications from comments
Visual Context: Summary of screenshots/videos (what you observed in each)
Related Issues: How this connects to other work
Technical Context: Any PRs, code references, or documentation
Next Steps: Suggested approach based on all gathered context

Notes

The issue ID can be provided in formats like:
```
AI-1975
```
,
```
node-1975
```
, or just
```
1975
```
(will search)
If no issue ID is provided, ask the user for one

linear-issue

NPX Install

Tags

SKILL.md Content