linear-issue

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Linear Issue Analysis

Linear工单分析

Start work on Linear issue $ARGUMENTS

开始处理Linear工单**$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.

此技能依赖外部工具。在开始前，请确认以下工具是否可用：

必填项：

Linear MCP (
```
mcp__linear
```
)：必须已连接。没有它，该技能将完全无法运行。
GitHub CLI (
```
gh
```
)：必须已安装并完成认证。运行
```
gh auth status
```
进行验证。用于获取关联的PR和工单。

可选项（缺失时会优雅降级）：

Notion MCP (
```
mcp__notion
```
)：仅当工单链接到Notion文档时需要。如果不可用，在总结中注明Notion链接，并告知用户手动查看。
Loom转录技能 (
```
/loom-transcript
```
)：仅当工单包含Loom视频时需要。如果不可用，在总结中注明Loom链接，供用户自行观看。
curl：用于下载图片。几乎总是可用；如果缺失，跳过图片下载并注明。

如果缺失任何必填工具，请停止操作并告知用户需要先完成哪些设置才能继续。

Instructions

操作步骤

Follow these steps to gather comprehensive context about the issue:

请按照以下步骤收集工单的全面上下文：

1. Fetch the Issue and Comments from Linear

1. 从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.

使用Linear MCP工具获取工单详情和评论：

使用
```
mcp__linear__get_issue
```
工具，传入工单ID以获取包含附件在内的完整详情
包含关联关系，查看阻塞/相关/重复工单
获取工单详情后立即使用
```
mcp__linear__list_comments
```
工具，传入工单ID以获取所有评论

应在同一步骤中同时调用这两个工具，以提前收集完整上下文。

2. Analyze Attachments and Media (MANDATORY)

2. 分析附件和媒体（必填步骤）

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

重要提示： 此步骤为必填项，不可跳过。您必须扫描并获取工单描述和所有评论中的所有可视化内容。

截图/图片（必须获取）：

扫描工单描述和所有评论中的所有图片URL：
- ```
<img>
```
  标签
- Markdown图片
```
![](url)
```
- 原始URL（github.com/user-attachments、imgur.com等）
对于找到的每张图片（无论是在描述还是评论中）：
- 使用
```
curl -sL "url" -o /path/to/image.png
```
  下载（GitHub URL需要跟随重定向）
- 使用
```
Read
```
  工具查看下载的文件
- 详细描述您看到的内容
请勿跳过图片——它们通常包含关键上下文，比如错误信息、UI状态或配置

Loom视频（必须获取转录文本）：

扫描工单描述和所有评论中的Loom URL（loom.com/share/...）
对于找到的每个Loom视频（无论是在描述还是评论中）：
- 使用
```
/loom-transcript
```
  技能获取完整转录文本
- 总结关键点、时间戳以及任何演示的问题
Loom视频通常包含文本无法传达的关键复现步骤和上下文

3. Fetch Related Context

3. 获取相关上下文

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

关联的Linear工单：

对关联关系中提到的所有工单，使用
```
mcp__linear__get_issue
```
工具获取详情
总结它们与主工单的关联方式

GitHub PR和工单：

如果提到GitHub链接，使用
```
gh
```
CLI获取PR/工单详情：
- ```
gh pr view <number>
```
  用于拉取请求
- ```
gh issue view <number>
```
  用于工单

下载工单附件中的图片：

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

Notion文档：

如果存在Notion链接，使用
```
mcp__notion__notion-fetch
```
工具，传入Notion URL或页面ID以获取文档内容
总结相关文档内容

4. Review Comments

4. 审核评论

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

评论已在步骤1中获取。审核时需注意：

额外的上下文和讨论历史
评论中链接的任何附件或媒体（按照步骤2处理）
对原始工单描述的澄清或更新

5. Present Summary

5. 呈现总结

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

呈现前，请确认已完成以下操作：

下载并查看了描述和评论中的所有图片
获取了描述和评论中所有Loom视频的转录文本
通过
```
gh
```
CLI获取了所有关联的GitHub工单/PR
列出了工单的所有评论

收集完所有上下文后，呈现全面的总结，包括：

工单概览：标题、状态、优先级、经办人、标签
描述：完整的工单描述，以及评论中的任何澄清内容
可视化上下文：截图/视频的总结（每个内容中的观察结果）
关联工单：与其他工作的关联方式
技术上下文：任何PR、代码引用或文档
下一步建议：基于收集到的所有上下文给出的建议处理方式

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

工单ID可以是以下格式：
```
AI-1975
```
、
```
node-1975
```
或仅
```
1975
```
（系统会自动搜索）
如果未提供工单ID，请向用户索要