Loading...

Back to Details

linear

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Linear Issue Management

Linear问题管理

Before using Linear workflows, search for

linear

MCP tools. If not found, treat as not installed.

在使用Linear工作流之前，请先搜索

linear

MCP工具。如果未找到，则视为未安装。

⚠️ CRITICAL: PR Creation with Linear Issues

⚠️ 重要提醒：关联Linear问题的PR创建规范

When creating a PR that references Linear issues (LOBE-xxx), you MUST:

Create the PR with magic keywords (
```
Fixes LOBE-xxx
```
)
IMMEDIATELY after PR creation, add completion comments to ALL referenced Linear issues
Do NOT consider the task complete until Linear comments are added

This is NON-NEGOTIABLE. Skipping Linear comments is a workflow violation.

当创建关联Linear问题（LOBE-xxx格式）的PR时，必须执行以下步骤：

使用魔法关键词创建PR（例如
```
Fixes LOBE-xxx
```
）
PR创建完成后立即，为所有关联的Linear问题添加完成说明评论
只有添加了Linear评论后，才能视为任务完成

这是硬性要求，跳过Linear评论属于违反工作流规范。

Workflow

工作流

Retrieve issue details before starting:
```
mcp__linear-server__get_issue
```
Check for sub-issues: Use
```
mcp__linear-server__list_issues
```
with
```
parentId
```
filter
Update issue status when completing:
```
mcp__linear-server__update_issue
```
Add completion comment (REQUIRED):
```
mcp__linear-server__create_comment
```

开始前检索问题详情：调用
```
mcp__linear-server__get_issue
```
检查子问题：使用带
```
parentId
```
过滤器的
```
mcp__linear-server__list_issues
```
完成时更新问题状态：调用
```
mcp__linear-server__update_issue
```
添加完成评论（必填）：调用
```
mcp__linear-server__create_comment
```

Creating Issues

创建问题

When creating issues with

mcp__linear-server__create_issue

, MUST add the
claude code
label.

使用

mcp__linear-server__create_issue

创建问题时，必须添加
claude code
标签。

Completion Comment Format

完成评论格式

Every completed issue MUST have a comment summarizing work done:

markdown

undefined

每个已完成的问题必须添加一条总结工作内容的评论，格式如下：

markdown

undefined

Changes Summary

变更总结

Feature: Brief description of what was implemented
Files Changed: List key files modified
PR: #xxx or PR URL

功能：简要描述实现的内容
修改文件：列出关键修改的文件
PR：#xxx 或 PR链接

Key Changes

主要变更

Change 1
Change 2
...


This is critical for:

- Team visibility
- Code review context
- Future reference

变更点1
变更点2
...


这对于以下方面至关重要：

- 团队可见性
- 代码评审上下文
- 未来参考

PR Association (REQUIRED)

PR关联要求（必填）

When creating PRs for Linear issues, include magic keywords in PR body:

```
Fixes LOBE-123
```
```
Closes LOBE-123
```
```
Resolves LOBE-123
```

为Linear问题创建PR时，请在PR正文中包含以下魔法关键词：

```
Fixes LOBE-123
```
```
Closes LOBE-123
```
```
Resolves LOBE-123
```

Per-Issue Completion Rule

单问题完成规则

When working on multiple issues, update EACH issue IMMEDIATELY after completing it:

Complete implementation
Run
```
bun run type-check
```
Run related tests
Create PR if needed
Update status to "In Review" (NOT "Done")
Add completion comment immediately
Move to next issue

Note: Status → "In Review" when PR created. "Done" only after PR merged.

❌ Wrong: Complete all → Create PR → Forget Linear comments

✅ Correct: Complete → Create PR → Add Linear comments → Task done

当处理多个问题时，每个问题完成后必须立即更新：

完成功能实现
运行
```
bun run type-check
```
运行相关测试
如有需要创建PR
将状态更新为**"评审中"（不要设为"已完成"）**
立即添加完成评论
开始处理下一个问题

注意：创建PR后将状态设为"评审中"，只有PR合并后才能设为"已完成"。

❌ 错误做法：完成所有问题 → 创建PR → 忘记添加Linear评论

✅ 正确做法：完成单个问题 → 创建PR → 添加Linear评论 → 标记该任务完成