Back to Details

linear

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Linear

Linear

Overview

概述

This skill provides a structured workflow for managing issues, projects & team workflows in Linear. It ensures consistent integration with the Linear MCP server, which offers natural-language project management for issues, projects, documentation, and team collaboration.
该Skill为在Linear中管理问题、项目及团队工作流提供了结构化的工作流程。它确保与Linear MCP服务器的集成一致性，该服务器为问题、项目、文档和团队协作提供自然语言项目管理功能。

Prerequisites

前提条件

  • Linear MCP server must be connected and accessible via OAuth
  • Confirm access to the relevant Linear workspace, teams, and projects
  • 必须通过OAuth连接并可访问Linear MCP服务器
  • 确认拥有相关Linear工作区、团队和项目的访问权限

Required Workflow

必选工作流程

Follow these steps in order. Do not skip steps.
请按顺序执行以下步骤，请勿跳过。

Step 0: Set up Linear MCP (if not already configured)

步骤0：设置Linear MCP（若尚未配置）

If any MCP call fails because Linear MCP is not connected, pause and set it up:
  1. Add the Linear MCP: 
    • codex mcp add linear --url https://mcp.linear.app/mcp
  2. Enable remote MCP client:
    • Set 
      [features] rmcp_client = true
      in 
      config.toml
      or run 
      codex --enable rmcp_client
  3. Log in with OAuth: 
    • codex mcp login linear
After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
Windows/WSL note: If you see connection errors on Windows, try configuring the Linear MCP to run via WSL:
json
{"mcpServers": {"linear": {"command": "wsl", "args": ["npx", "-y", "mcp-remote", "https://mcp.linear.app/sse", "--transport", "sse-only"]}}}
如果由于Linear MCP未连接导致任何MCP调用失败，请暂停并进行设置：
  1. 添加Linear MCP： 
    • codex mcp add linear --url https://mcp.linear.app/mcp
  2. 启用远程MCP客户端：
    • 在
      config.toml
      中设置
      [features] rmcp_client = true
      或 运行
      codex --enable rmcp_client
  3. 通过OAuth登录： 
    • codex mcp login linear
登录成功后，用户需要重启codex。当用户再次尝试时，你应完成当前回复并告知他们可以继续执行步骤1。
**Windows/WSL注意事项：**如果在Windows上遇到连接错误，尝试配置Linear MCP通过WSL运行：
json
{"mcpServers": {"linear": {"command": "wsl", "args": ["npx", "-y", "mcp-remote", "https://mcp.linear.app/sse", "--transport", "sse-only"]}}}

Step 1

步骤1

Clarify the user's goal and scope (e.g., issue triage, sprint planning, documentation audit, workload balance). Confirm team/project, priority, labels, cycle, and due dates as needed.
明确用户的目标和范围（例如，问题分类、冲刺规划、文档审核、工作量平衡）。根据需要确认团队/项目、优先级、标签、周期和截止日期。

Step 2

步骤2

Select the appropriate workflow (see Practical Workflows below) and identify the Linear MCP tools you will need. Confirm required identifiers (issue ID, project ID, team key) before calling tools.
选择合适的工作流程（见下方实用工作流程）并确定所需的Linear MCP工具。在调用工具前确认所需的标识符（工单ID、项目ID、团队密钥）。

Step 3

步骤3

Execute Linear MCP tool calls in logical batches:
  • Read first (list/get/search) to build context.
  • Create or update next (issues, projects, labels, comments) with all required fields.
  • For bulk operations, explain the grouping logic before applying changes.
按逻辑批次执行Linear MCP工具调用：
  • 先读取（列出/获取/搜索）以构建上下文。
  • 接下来创建或更新（工单、项目、标签、评论），并填写所有必填字段。
  • 对于批量操作，在应用更改前说明分组逻辑。

Step 4

步骤4

Summarize results, call out remaining gaps or blockers, and propose next actions (additional issues, label changes, assignments, or follow-up comments).
总结结果，指出剩余的空白或障碍，并提出后续操作建议（新增工单、标签变更、任务分配或跟进评论）。

Available Tools

可用工具

Issue Management: 
list_issues
, 
get_issue
, 
create_issue
, 
update_issue
, 
list_my_issues
, 
list_issue_statuses
, 
list_issue_labels
, 
create_issue_label
Project & Team: 
list_projects
, 
get_project
, 
create_project
, 
update_project
, 
list_teams
, 
get_team
, 
list_users
Documentation & Collaboration: 
list_documents
, 
get_document
, 
search_documentation
, 
list_comments
, 
create_comment
, 
list_cycles
工单管理：
list_issues
, 
get_issue
, 
create_issue
, 
update_issue
, 
list_my_issues
, 
list_issue_statuses
, 
list_issue_labels
, 
create_issue_label
项目与团队：
list_projects
, 
get_project
, 
create_project
, 
update_project
, 
list_teams
, 
get_team
, 
list_users
文档与协作：
list_documents
, 
get_document
, 
search_documentation
, 
list_comments
, 
create_comment
, 
list_cycles

Practical Workflows

实用工作流程

  • Sprint Planning: Review open issues for a target team, pick top items by priority, and create a new cycle (e.g., "Q1 Performance Sprint") with assignments.
  • Bug Triage: List critical/high-priority bugs, rank by user impact, and move the top items to "In Progress."
  • Documentation Audit: Search documentation (e.g., API auth), then open labeled "documentation" issues for gaps or outdated sections with detailed fixes.
  • Team Workload Balance: Group active issues by assignee, flag anyone with high load, and suggest or apply redistributions.
  • Release Planning: Create a project (e.g., "v2.0 Release") with milestones (feature freeze, beta, docs, launch) and generate issues with estimates.
  • Cross-Project Dependencies: Find all "blocked" issues, identify blockers, and create linked issues if missing.
  • Automated Status Updates: Find your issues with stale updates and add status comments based on current state/blockers.
  • Smart Labeling: Analyze unlabeled issues, suggest/apply labels, and create missing label categories.
  • Sprint Retrospectives: Generate a report for the last completed cycle, note completed vs. pushed work, and open discussion issues for patterns.
  • 冲刺规划：查看目标团队的未结工单，按优先级挑选重点事项，并创建带有任务分配的新周期（例如，"Q1性能冲刺"）。
  • 缺陷分类：列出严重/高优先级缺陷，按用户影响程度排序，并将顶部事项移至"进行中"状态。
  • 文档审核：搜索文档（例如，API认证），然后为存在空白或过时的部分创建标记为"documentation"的工单，并附上详细修复方案。
  • 团队工作量平衡：按经办人分组活跃工单，标记出工作量过大的人员，并建议或进行任务重新分配。
  • 发布规划：创建一个项目（例如，"v2.0版本发布"），包含里程碑（功能冻结、测试版、文档、上线）并生成带有预估工时的工单。
  • 跨项目依赖关系：查找所有"已阻塞"的工单，识别阻塞因素，若缺失则创建关联工单。
  • 自动化状态更新：查找你名下状态更新停滞的工单，并根据当前状态/阻塞因素添加状态评论。
  • 智能标签：分析未标记的工单，建议/应用标签，并创建缺失的标签类别。
  • 冲刺回顾：为上一个已完成的周期生成报告，记录已完成与延期的工作，并开启针对模式的讨论工单。

Tips for Maximum Productivity

高效使用技巧

  • Batch operations for related changes; consider smart templates for recurring issue structures.
  • Use natural queries when possible ("Show me what John is working on this week").
  • Leverage context: reference prior issues in new requests.
  • Break large updates into smaller batches to avoid rate limits; cache or reuse filters when listing frequently.
  • 批量处理相关变更；为重复出现的工单结构考虑使用智能模板。
  • 尽可能使用自然语言查询（例如，"显示John本周正在处理的工作"）。
  • 利用上下文：在新请求中引用之前的工单。
  • 将大型拆分为较小的批次以避免触发速率限制；当频繁列出数据时，缓存或重复使用筛选条件。

Troubleshooting

故障排除

  • Authentication: Clear browser cookies, re-run OAuth, verify workspace permissions, ensure API access is enabled.
  • Tool Calling Errors: Confirm the model supports multiple tool calls, provide all required fields, and split complex requests.
  • Missing Data: Refresh token, verify workspace access, check for archived projects, and confirm correct team selection.
  • Performance: Remember Linear API rate limits; batch bulk operations, use specific filters, or cache frequent queries.
  • 认证问题：清除浏览器Cookie，重新运行OAuth，验证工作区权限，确保API访问已启用。
  • 工具调用错误：确认模型支持多工具调用，提供所有必填字段，并拆分复杂请求。
  • 数据缺失：刷新令牌，验证工作区访问权限，检查是否存在已归档的项目，并确认团队选择正确。
  • 性能问题：记住Linear API的速率限制；批量处理批量操作，使用特定筛选条件，或缓存频繁查询的结果。