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工具。如果未找到,则视为未安装。

Workflow

工作流

  1. Retrieve issue details before starting:
    mcp__linear-server__get_issue
  2. Check for sub-issues: Use
    mcp__linear-server__list_issues
    with
    parentId
    filter
  3. Update issue status when completing:
    mcp__linear-server__update_issue
  4. Add completion comment (REQUIRED):
    mcp__linear-server__create_comment
  1. 开始前检索问题详情
    mcp__linear-server__get_issue
  2. 检查子问题:使用带
    parentId
    过滤器的
    mcp__linear-server__list_issues
  3. 完成时更新问题状态
    mcp__linear-server__update_issue
  4. 添加完成评论(必填)
    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 (REQUIRED)

完成评论(必填)

Every completed issue MUST have a comment summarizing work done. This is critical for:
  • Team visibility
  • Code review context
  • Future reference
每个已完成的问题都必须有一条总结工作内容的评论。这对以下方面至关重要:
  • 团队可见性
  • 代码评审上下文
  • 未来参考

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:
  1. Complete implementation
  2. Run
    bun run type-check
  3. Run related tests
  4. Create PR if needed
  5. Update status to "In Review" (NOT "Done")
  6. Add completion comment
  7. Move to next issue
Note: Status → "In Review" when PR created. "Done" only after PR merged.
❌ Wrong: Complete all → Update all statuses → Add all comments
✅ Correct: Complete A → Update A → Comment A → Complete B → ...
处理多个问题时,完成每个问题后立即更新该问题:
  1. 完成实现
  2. 运行
    bun run type-check
  3. 运行相关测试
  4. 如有需要创建PR
  5. 将状态更新为**“In Review”(而非“Done”)**
  6. 添加完成评论
  7. 处理下一个问题
注意:创建PR后将状态改为“In Review”。仅当PR合并后才改为“Done”。
❌ 错误做法:完成所有问题 → 更新所有状态 → 添加所有评论
✅ 正确做法:完成问题A → 更新问题A → 为问题A添加评论 → 完成问题B → ...