linear-dev-accelerator

Linear 开发加速器

一项全面的技能，通过集成 MCP 服务，利用 Linear 项目管理加速软件开发。此技能可帮助快速设置项目、智能管理问题，并简化 Web 和移动应用的开发工作流。

何时使用此技能

在以下情况下使用此技能：

• 启动新的软件开发项目，需要设置 Linear 项目管理
• 管理前端、后端或全栈应用的问题、任务和功能
• 将开发工作组织到 Sprint／周期中，并进行适当跟踪
• 与开发团队协作开展软件项目
• 在开发过程中自动执行项目管理任务
• 系统地跟踪 Bug、功能和技术债务
• 通过结构化的项目管理工作流构建应用
• 将 Linear 与 GitHub 集成，以基于 PR 的方式开展开发

核心概念

Linear 项目管理理念

Linear 强调软件团队的速度、清晰度和专注度：

• 问题作为一等对象：每项工作都是带有丰富元数据的问题
• 通过周期规划 Sprint：有时限的迭代，专注于执行
• 通过项目规划产品：更高层级的计划和路线图
• 通过团队组织工作：为不同职能或产品设立的工作区
• 通过工作流管理流程：自定义状态，以匹配你的开发流程

Linear 核心实体

1. 团队：组织单位（例如：前端、后端、移动端）
2. 问题：单项任务、Bug、功能或改进
3. 项目：为更大型计划汇集相关问题的集合
4. 周期：有时限的迭代（类似于 Sprint）
5. 标签：分类和筛选机制
6. 状态：问题状态（待办列表、待处理、进行中、审核中、已完成、已取消）
7. 评论：围绕问题开展协作和讨论
8. 文档：与问题集成的长篇文档

MCP 服务工具参考

问题管理

list_issues

列出并筛选工作区中的问题。

常用参数：

team: Team name or ID
assignee: User ID, name, email, or "me" for your issues
state: Status name or ID (e.g., "In Progress", "Done")
label: Label name or ID for filtering
project: Project name or ID
query: Search in title/description
limit: Number of results (max 250, default 50)
orderBy: "createdAt" or "updatedAt" (default)
includeArchived: Include archived issues (default: true)

示例：

# Get my current issues
assignee: "me"
state: "In Progress"
limit: 10

# Find bugs in a specific project
label: "bug"
project: "Mobile App"
state: "Todo"

# Search for authentication-related issues
query: "authentication"
team: "Backend"

create_issue

创建包含完整元数据的新问题。

必需参数：

title: Issue title (clear and concise)
team: Team name or ID

可选参数：

description: Markdown description with details
assignee: User ID, name, email, or "me"
state: State type, name, or ID
priority: 0=None, 1=Urgent, 2=High, 3=Normal, 4=Low
labels: Array of label names or IDs
project: Project name or ID
cycle: Cycle name, number, or ID
parentId: Parent issue ID for sub-issues
dueDate: ISO format date
links: Array of {url, title} objects

示例：

title: "Implement user authentication"
team: "Backend"
description: |
  ## Overview
  Add JWT-based authentication to the API

  ## Tasks
  - [ ] Design auth flow
  - [ ] Implement JWT tokens
  - [ ] Add refresh token logic
  - [ ] Write tests

  ## Acceptance Criteria
  - Secure token generation
  - Token expiration handling
  - Proper error responses
assignee: "me"
priority: 2  # High
labels: ["feature", "authentication", "backend"]
project: "API v2.0"

update_issue

更新现有问题。

必需参数： id（问题 ID）

可更新字段：

title, description, assignee, state, priority, labels,
project, cycle, parentId, dueDate, estimate, links

示例：

id: "issue-uuid-here"
state: "In Progress"
assignee: "me"
labels: ["feature", "in-development"]

get_issue

获取问题详情，包括附件和 Git 分支。

参数：

id: Issue ID

**返回：**完整的问题详情，包括附件、Git 分支名称及相关数据

项目管理

list_projects

列出并筛选项目。

参数：

team: Team name or ID
state: State name or ID
member: User ID, name, email, or "me"
initiative: Initiative name or ID
query: Search project names
limit: Number of results (max 250, default 50)
orderBy: "createdAt" or "updatedAt"
includeArchived: Include archived (default: false)

create_project

创建新项目。

必需参数：

name: Project name
team: Team name or ID

可选参数：

description: Full Markdown description
summary: Concise plaintext summary (max 255 chars)
lead: Project lead (User ID, name, email, or "me")
state: Project state
priority: 0-4 (None, Urgent, High, Medium, Low)
startDate: ISO format date
targetDate: ISO format date
labels: Array of label names or IDs

示例：

name: "Mobile App v2.0"
team: "Mobile"
summary: "Complete redesign of mobile app with new features"
description: |
  # Mobile App v2.0

  ## Goals
  - Modern UI/UX redesign
  - Offline-first architecture
  - Push notifications
  - Real-time sync

  ## Timeline
  Q1 2025 - Design & Planning
  Q2 2025 - Development
  Q3 2025 - Testing & Launch
lead: "me"
priority: 2
startDate: "2025-01-15"
targetDate: "2025-09-30"
labels: ["mobile", "redesign", "major-release"]

update_project

更新现有项目详情。

必需参数： id（项目 ID）

**可更新字段：**名称、描述、摘要、负责人、状态、优先级、开始日期、目标日期、标签

get_project

获取项目详情。

参数：

query: Project ID or name

标签与分类

list_issue_labels

列出可用标签。

参数：

team: Team name or ID (optional, for team-specific labels)
name: Filter by label name
limit: Number of results (max 250)
orderBy: "createdAt" or "updatedAt"

create_issue_label

创建用于分类的新标签。

必需参数：

name: Label name

可选参数：

color: Hex color code (e.g., "#10B981")
description: Label description
teamId: Team UUID (omit for workspace label)
isGroup: true for label groups (default: false)
parentId: Parent label UUID for hierarchical labels

示例：

name: "frontend"
color: "#3B82F6"
description: "Frontend-related tasks and features"
teamId: "team-uuid-here"

工作流与状态管理

list_issue_statuses

列出团队的可用状态。

参数：

team: Team name or ID (required)

**返回：**包含 id、type、name 的状态数组

• 类型：待办列表、未开始、已开始、已完成、已取消

get_issue_status

获取状态详情。

参数：

id: Status ID
name: Status name
team: Team name or ID (required)

协作

list_comments

列出问题上的评论。

参数：

issueId: Issue ID (required)

create_comment

向问题添加评论。

参数：

issueId: Issue ID (required)
body: Markdown comment content (required)
parentId: Parent comment ID for replies (optional)

示例：

issueId: "issue-uuid-here"
body: |
  Great progress! A few notes:

  - Consider edge case for expired tokens
  - Add integration test for refresh flow
  - Document the auth header format

团队与用户管理

list_teams

列出工作区中的所有团队。

参数：

query: Search query (optional)
limit: Number of results (max 250)
includeArchived: Include archived teams (default: false)

get_team

获取详细的团队信息。

参数：

query: Team UUID, key, or name

list_users

列出工作区中的用户。

参数：

query: Filter by name or email (optional)

get_user

获取用户详细信息。

参数：

query: User ID, name, email, or "me"

周期（冲刺规划）

list_cycles

获取团队的周期。

参数：

teamId: Team ID (required)
type: "current", "previous", "next", or omit for all

文档

list_documents

列出 Linear 文档。

参数：

query: Search query
creatorId: Creator user ID
projectId: Project ID
initiativeId: Initiative ID
limit: Number of results (max 250)
orderBy: "createdAt" or "updatedAt"
includeArchived: Include archived (default: false)

get_document

按 ID 或 slug 获取文档。

参数：

id: Document ID or slug

开发工作流模式

模式 1：新功能开发

**场景：**为 Web 应用构建新功能

1. Create feature issue
   - Use create_issue with:
     - Clear title: "Add dark mode toggle"
     - Detailed description with tasks and acceptance criteria
     - Assign to yourself or team member
     - Add labels: ["feature", "frontend", "ui"]
     - Link to project: "Q1 Features"
     - Set priority based on urgency

2. Break down into sub-tasks (if complex)
   - Create child issues with parentId
   - Each sub-task is a manageable unit of work
   - Example sub-tasks:
     - "Design dark mode color scheme"
     - "Implement theme context in React"
     - "Add toggle button component"
     - "Persist theme preference"

3. Track progress
   - Update issue state as you work:
     - Todo → In Progress → In Review → Done
   - Add comments with updates and blockers
   - Link PR when ready for review

4. Complete and review
   - Update state to "In Review"
   - Add links to PR, deployed preview
   - Mark as Done when merged and deployed

模式 2：Bug 分类与修复

**场景：**高效处理 Bug 报告

1. Create bug issue
   - title: Clear description of the bug
   - description: Steps to reproduce, expected/actual behavior
   - labels: ["bug", "priority:high"] if critical
   - assignee: Developer responsible for that area
   - Add links to error logs, screenshots

2. Investigation
   - Update to "In Progress"
   - Add comments with findings
   - Link to related issues if discovered
   - Update priority if needed

3. Fix implementation
   - Reference issue in commit messages
   - Link PR to issue
   - Add comment explaining fix approach

4. Verification and closure
   - State: "In Review" during QA
   - State: "Done" after verification
   - Add comment confirming fix is deployed

模式 3：冲刺／周期规划

**场景：**规划一个为期 2 周的开发周期

1. Review backlog
   - list_issues with state: "Backlog"
   - Filter by priority and labels
   - Identify issues ready for development

2. Create or select cycle
   - list_cycles to see current cycle
   - Organize selected issues into cycle

3. Assign and prioritize
   - Distribute issues across team
   - Set priorities: Urgent (1) → High (2) → Normal (3)
   - Balance workload across team members

4. Daily tracking
   - list_issues with assignee: "me", state: "In Progress"
   - Update issue states as work progresses
   - Add comments for standup updates
   - Move blocked issues back to Todo

5. Cycle review
   - List completed issues in cycle
   - Review metrics (velocity, completion rate)
   - Move incomplete issues to next cycle or backlog

模式 4：新应用项目设置

**场景：**启动一个新的移动应用项目

1. Create project
   - name: "Mobile App - iOS & Android"
   - description: Full project scope, goals, timeline
   - Set lead, dates, labels
   - Link to design docs, PRD

2. Set up project structure
   - Create initial issues for setup:
     - "Setup React Native project"
     - "Configure CI/CD pipeline"
     - "Design component architecture"
     - "Setup state management"
   - Assign to team members
   - Add to project

3. Create epics (major features)
   - Authentication system
   - User profile management
   - Core app functionality
   - Push notifications
   - Each epic is a parent issue with sub-issues

4. Organize into cycles
   - Cycle 1: Project setup & architecture
   - Cycle 2-3: Core features
   - Cycle 4: Polish & testing
   - Assign issues to appropriate cycles

5. Track progress
   - Update project description with status
   - Weekly reviews with get_project
   - Adjust priorities and timeline as needed

模式 5：GitHub 集成工作流

**场景：**将 Linear 事项与 GitHub PR 关联

1. Create issue in Linear
   - Get git branch name from issue: issue.gitBranchName
   - Example: "cetiaiservices/cet-95-create-benchmark-methodology-guide"

2. Create branch using Linear's suggested name
   - Ensures automatic linking
   - Linear tracks PR status automatically

3. Development
   - Commit with Linear issue reference: "CET-95: Add benchmark docs"
   - Linear updates issue automatically when PR created

4. Code review
   - PR opened → Linear sets state to "In Review"
   - Comments on PR can sync to Linear
   - Review feedback tracked in both systems

5. Merge and deploy
   - PR merged → Linear can auto-complete issue
   - Deployment triggers update Linear with links
   - Full traceability from issue → PR → deployment

加速开发策略

策略 1：批量创建事项

启动项目时，一次性创建所有已知事项：

// Create multiple related issues
const features = [
  "User registration and login",
  "Password reset flow",
  "Email verification",
  "Social auth (Google, GitHub)",
  "Two-factor authentication"
];

// For each feature, create issue with:
- Consistent labeling: ["auth", "feature"]
- Link to parent project: "Authentication System"
- Assign to team members based on expertise
- Set due dates based on project timeline

策略 2：使用智能筛选聚焦重点

使用筛选条件降低认知负担：

// Morning: What do I need to work on today?
assignee: "me"
state: "In Progress"
orderBy: "updatedAt"

// Planning: What's in the backlog for my team?
team: "Frontend"
state: "Backlog"
priority: 2  // High priority items
labels: ["ready-for-dev"]

// Review: What needs my attention?
assignee: "me"
state: "In Review"
orderBy: "createdAt"  // Oldest first

策略 3：基于模板创建事项

使用模板创建格式一致的事项：

// Bug report template
title: "[BUG] {concise description}"
description: |
  ## Bug Description
  {What's wrong?}

  ## Steps to Reproduce
  1. {Step 1}
  2. {Step 2}
  3. {Step 3}

  ## Expected Behavior
  {What should happen}

  ## Actual Behavior
  {What actually happens}

  ## Environment
  - Browser: {browser}
  - OS: {OS}
  - Version: {version}

  ## Additional Context
  {Screenshots, logs, etc.}
labels: ["bug", "needs-triage"]
priority: 3  // Default to normal, adjust after triage

// Feature request template
title: "[FEATURE] {feature name}"
description: |
  ## Feature Description
  {What feature do you want?}

  ## User Story
  As a {user type}
  I want {goal}
  So that {benefit}

  ## Acceptance Criteria
  - [ ] {Criterion 1}
  - [ ] {Criterion 2}
  - [ ] {Criterion 3}

  ## Design Notes
  {Link to designs, wireframes}

  ## Technical Notes
  {Implementation considerations}
labels: ["feature", "needs-refinement"]

策略 4：自动更新状态

将事项更新纳入开发工作流：

// In CI/CD pipeline:
- Tests passing → Add comment with test results
- Deploy to staging → Update with staging URL
- Deploy to production → Mark as Done, add production URL

// In git hooks:
- Pre-commit: Verify issue reference in commit message
- Post-merge: Update Linear issue status
- Tag creation: Link release to completed issues

策略 5：跨职能协作

使用 Linear 协调前端／后端／移动端工作：

// Create parent issue for full-stack feature
Parent: "User Dashboard Feature"
  ├─ Child: "[Backend] Dashboard API endpoints"
  │   └─ labels: ["backend", "api"]
  ├─ Child: "[Frontend] Dashboard React components"
  │   └─ labels: ["frontend", "react"]
  └─ Child: "[Mobile] Dashboard mobile screens"
      └─ labels: ["mobile", "flutter"]

// Track dependencies
- Backend issue must complete first
- Frontend/Mobile can work in parallel after API ready
- Use "blocked" relation type to track dependencies

最佳实践

创建事项

1. 标题明确：以动词开头（添加、修复、更新、重构）
2. 描述详尽：使用 Markdown、检查清单和代码块
3. 正确标记：使用一致的标签体系
4. 合理拆分：事项应能在 1-3 天内完成
5. 验收标准：始终定义“完成”的标准

项目组织

1. 每项计划对应一个项目：不要创建过多项目
2. 使用标签进行分类：比项目更灵活
3. 定期清理：归档已完成的项目
4. 明确负责人：每个项目都需要一位负责人
5. 关联文档：及时更新项目描述

工作流管理

1. 限制进行中的工作：每人最多有 3 个“进行中”事项
2. 及时更新状态：保持事项状态最新
3. 积极使用评论：记录决策和阻碍因素
4. 关联相关事项：通过关联关系补充上下文
5. 完整完成事项：不要遗留长期无人处理的事项

团队协作

1. 明确分配：每个事项都应有一位负责人
2. 使用 @mentions：在评论中标记相关人员，让他们知悉
3. 定期评审：每周评审项目／周期
4. 庆祝成果：标记里程碑和成就
5. 共享上下文：关联 PR、文档和设计稿

标签体系

建议的标签类别：

Type Labels:
- feature, bug, improvement, docs, refactor, test

Priority Labels:
- priority:urgent, priority:high, priority:normal, priority:low

Area Labels:
- frontend, backend, mobile, devops, design, qa

Status Labels:
- blocked, ready-for-dev, needs-review, waiting-on-qa

Technology Labels:
- react, flutter, python, node, postgres, redis

与开发工具集成

GitHub 集成

• 使用 Linear 推荐的 Git 分支名称
• 在提交消息中引用 Linear 事项：“CET-123：添加功能”
• PR 会自动关联到 Linear 事项
• PR 状态会更新 Linear 事项状态
• 合并事件可以自动完成事项

CI/CD 集成

• 将测试结果作为评论发布到 Linear 事项
• 在部署事件发生时更新事项
• 在事项评论中关联部署 URL
• 按事项跟踪部署状态

Slack 集成

• 接收已分配事项的通知
• 从 Slack 更新 Linear
• 在团队频道中分享事项链接
• 获取包含个人事项的每日站会提醒

不同类型应用的常见工作流

前端应用开发

1. Design → Development workflow:
   - Create issue from design handoff
   - labels: ["frontend", "ui", "design-ready"]
   - Link to Figma/design files
   - Break into component-level issues

2. Component development:
   - Parent: "User Profile Page"
     ├─ "ProfileHeader component"
     ├─ "ProfileStats component"
     ├─ "ProfileSettings component"
     └─ "Profile routing and layout"

3. Integration and testing:
   - Create issues for:
     - Integration testing
     - Accessibility audit
     - Performance optimization
     - Browser compatibility testing

全栈应用开发

1. Feature planning:
   - Parent issue: "Payment Processing Feature"
   - Children:
     - Database schema design
     - API endpoint implementation
     - Frontend payment form
     - Payment provider integration
     - Error handling and logging
     - Testing (unit, integration, E2E)

2. Parallel development:
   - Backend team: API and database
   - Frontend team: UI components (mocked API)
   - Coordinate through Linear comments
   - Track blockers and dependencies

3. Integration phase:
   - Create integration testing issue
   - Link all related issues
   - Coordinate deployment

移动应用开发

1. Platform-specific tracking:
   - labels: ["ios", "android", "shared"]
   - Track platform-specific bugs separately
   - Share code issues labeled "shared"

2. Release management:
   - Project per release: "iOS v2.1.0"
   - Issues per feature/fix in release
   - Track App Store/Play Store submissions
   - Link to release notes

3. Testing workflow:
   - Device testing: Track per device type
   - OS version compatibility
   - Performance on different hardware
   - Beta testing feedback

故障排除

常见问题

筛选结果中未显示问题

• 检查问题是否已归档：设置 includeArchived: true
• 确认团队名称/ID 是否正确
• 检查状态是否符合预期

无法创建问题

• 确保已提供团队参数（必填）
• 如果使用标签，请确认标签名称存在
• 检查项目名称/ID 是否有效
• 确保受分配者存在于工作区中

无法更新问题

• 确认问题 ID 是否正确（先使用 get_issue）
• 检查你是否有权限修改问题
• 确保状态名称有效（使用 list_issue_statuses）
• 确认标签名称存在

项目未加载

• 检查 includeArchived 设置
• 确认团队筛选条件是否正确
• 尝试不使用筛选条件，以查看所有项目

高级用法

自动化项目设置

以编程方式创建完整的项目结构：

1. Create project
2. Create label set for project
3. Create epic issues (parent issues)
4. Create sub-issues for each epic
5. Assign issues to team members
6. Organize into first cycle
7. Generate project documentation

指标与报告

跟踪开发指标：

// Velocity tracking
- Issues completed per cycle
- Average time to complete
- Blockers frequency

// Quality metrics
- Bug rate per feature
- Time to fix bugs
- Reopened issues

// Team metrics
- Issues per team member
- Workload balance
- Completion rates

自定义工作流

设计符合你流程的工作流：

// Example: Feature flag workflow
States:
1. Backlog (unstarted)
2. Ready for Dev (unstarted)
3. In Development (started)
4. In Review (started)
5. In QA (started)
6. Deployed with Flag (started)
7. Flag Enabled (started)
8. Monitoring (started)
9. Flag Removed (completed)
10. Done (completed)

快速参考

常用快捷键

My active work:
  assignee: "me", state: "In Progress"

Team backlog:
  team: "{team-name}", state: "Backlog", orderBy: "updatedAt"

High priority issues:
  priority: 2, state: "Todo", orderBy: "createdAt"

Recently updated:
  orderBy: "updatedAt", limit: 20

Bugs needing triage:
  label: "bug", state: "Backlog", orderBy: "createdAt"

问题创建模板

title: "[TYPE] Clear, actionable title"
description: |
  ## Overview
  {What and why}

  ## Tasks
  - [ ] Task 1
  - [ ] Task 2

  ## Acceptance Criteria
  - Criterion 1
  - Criterion 2
team: "{team-name}"
assignee: "me"
labels: ["{type}", "{area}", "{priority}"]
project: "{project-name}"
priority: 3

资源

• Linear 文档：https://linear.app/docs
• Linear API 参考：https://developers.linear.app/docs
• Linear 博客：https://linear.app/blog
• GitHub 集成指南：https://linear.app/docs/github
• Linear 键盘快捷键：linear.app/shortcuts

---

技能版本：1.0.0 最后更新：2025 年 10 月 技能类别：项目管理、开发提效、团队协作 兼容对象：Linear MCP Server、GitHub、CI/CD 流水线