菜单
This skill should be used when the user asks to "create a Linear issue", "file a ticket", "open a Linear ticket", "update a Linear issue", "check a Linear ticket", "add a label to a ticket", "assign an issue", "close a ticket", or any time a workflow step needs to create/read a Linear ticket. Also use when reading or writing ticket_id in state.yaml.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.
QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.
Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.
Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.
Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.
Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.
| name | linear |
| description | This skill should be used when the user asks to "create a Linear issue", "file a ticket", "open a Linear ticket", "update a Linear issue", "check a Linear ticket", "add a label to a ticket", "assign an issue", "close a ticket", or any time a workflow step needs to create/read a Linear ticket. Also use when reading or writing ticket_id in state.yaml. |
| user-invocable | true |
Provides Linear issue management via the plugin:linear MCP server.
Linear is driven entirely by the presence of a linear: block in the repo's
spec/project.yaml. There is no separate config step and no flag — if the
block is present, use it; if it is absent, skip every Linear call silently and
never block.
linear:
team_id: <uuid>
team_prefix: HL
project_id: <uuid>
product_label_id: <uuid> # repo-specific product label
If spec/project.yaml has no linear: block (or no file), do nothing — this
is the normal state for repos that use the backlog CLI instead.
All Linear operations go through the plugin:linear MCP server:
| Operation | Tool |
|---|---|
| Create or update an issue | mcp__plugin_linear_linear__save_issue |
| Fetch issue details | mcp__plugin_linear_linear__get_issue |
| Get issue status | mcp__plugin_linear_linear__get_issue_status |
| List issues | mcp__plugin_linear_linear__list_issues |
| Save a comment | mcp__plugin_linear_linear__save_comment |
| Delete a comment | mcp__plugin_linear_linear__delete_comment |
| List comments | mcp__plugin_linear_linear__list_comments |
| Get team info | mcp__plugin_linear_linear__get_team |
| Get project info | mcp__plugin_linear_linear__get_project |
| List projects | mcp__plugin_linear_linear__list_projects |
| List issue statuses | mcp__plugin_linear_linear__list_issue_statuses |
| List issue labels | mcp__plugin_linear_linear__list_issue_labels |
| Create an issue label | mcp__plugin_linear_linear__create_issue_label |
| Get user info | mcp__plugin_linear_linear__get_user |
| List users | mcp__plugin_linear_linear__list_users |
| List cycles | mcp__plugin_linear_linear__list_cycles |
| Get milestone | mcp__plugin_linear_linear__get_milestone |
| Save milestone | mcp__plugin_linear_linear__save_milestone |
| List milestones | mcp__plugin_linear_linear__list_milestones |
| Get document | mcp__plugin_linear_linear__get_document |
| List documents | mcp__plugin_linear_linear__list_documents |
| Search documentation | mcp__plugin_linear_linear__search_documentation |
| Get attachment | mcp__plugin_linear_linear__get_attachment |
| Create attachment | mcp__plugin_linear_linear__create_attachment |
| Delete attachment | mcp__plugin_linear_linear__delete_attachment |
| Extract images | mcp__plugin_linear_linear__extract_images |
spec/project.yaml. If there is no linear: block → skip silently.mcp__plugin_linear_linear__save_issue with:
title: concise description of the changedescription: summary from design.md, discovery.md, or user input (markdown supported)teamId: linear.team_idprojectId: linear.project_idlabelIds: linear.product_label_id + type label + complexity label$WORKFLOW_STATE_DIR/<feature>/state.yaml field ticket_id: HL-XXX.linear.product_label_id from spec/project.yamlUse mcp__plugin_linear_linear__list_issue_labels to resolve label names to UUIDs when not already known.
Call mcp__plugin_linear_linear__save_issue with id set to the existing ticket ID (e.g. HL-134).
Pass only the fields to change — the tool performs a partial update.
Common update scenarios:
stateId (resolve via list_issue_statuses)save_comment with issueIdstateId for the "Done" or "Cancelled" statemcp__plugin_linear_linear__get_issue { id: "HL-XXX" }
The response includes title, description, state, labels, assignee, and comments.
| Field | Description |
|---|---|
ticket_id | Primary issue ID (e.g. HL-134) |
Never invent ticket IDs. Use only values returned from MCP or provided by the user.
Add a linear: block to the repo's spec/project.yaml (team_id, team_prefix,
project_id, product_label_id) and create a matching product label in Linear.
No other wiring is required — the skill keys off that block alone.