菜单
Update one existing Linear issue through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use only as a narrow fallback when the normal Linear connector cannot add labels, assign a user, set a parent, update text, set issue priority, or set manual sort order.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Update one existing Linear Custom View through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use only as a narrow fallback when the normal Linear connector cannot update Custom View metadata or filters.
Change Linear issue statuses through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use when the user asks to move a Linear task or issue to Done, In Progress, Backlog, Todo, or another workflow state and the normal Linear MCP connector is unavailable, blocked, or insufficient.
Add one comment to a Linear issue through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use only as a narrow fallback when the normal Linear connector is unavailable or cannot create the comment.
Create one Linear issue through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use only as a narrow fallback when the normal Linear connector is unavailable or cannot create the issue.
Ensure one Linear Custom View exists through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use only as a narrow fallback when the normal Linear connector cannot set up a required view.
Read Linear Custom Views through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use when the user asks to inspect a Linear view URL, extract the live issue queue, preserve manual order, or use a Custom View as a source of task priority.
| name | linear-update-issue |
| description | Update one existing Linear issue through the direct Linear GraphQL API using a local LINEAR_API_KEY. Use only as a narrow fallback when the normal Linear connector cannot add labels, assign a user, set a parent, update text, set issue priority, or set manual sort order. |
| metadata | {"category":"productivity","capability_taxonomy_ids":["cap.productivity.issue_tracking","cap.tools.api_automation"],"compatibility":{"runtimes":["codex","claude_code","cursor","antigravity","windsurf"]},"distribution_scope":"public","invocation_strategy":"explicit","version":"v0.2","source_of_truth":"https://github.com/nicshik/linear-skills"} |
Use this skill when the normal Linear connector cannot perform a narrow update on one existing issue.
scripts/update_issue.py.--dry-run before live updates when checking labels, assignee, parent, text, priority, or manual sort order.--priority accepts none, no-priority, no_priority, urgent, high, medium, normal, low, or numeric 0..4.--sort-order updates Linear's workspace-wide manual issue order. Use it only after reading the relevant Custom View queue and preparing the full target order.When Codex sandboxing asks for approval because the script needs network access, request:
sandbox_permissions: require_escalatedprefix_rule: ["python3", "linear-update-issue/scripts/update_issue.py"]python3 scripts/update_issue.py LIN-123 --add-label Product --assignee "Alice Example" --dry-run --json
python3 scripts/update_issue.py LIN-123 --parent LIN-100 --append-description-file /path/to/note.md --json
python3 scripts/update_issue.py LIN-123 --priority high --dry-run --json
python3 scripts/update_issue.py LIN-123 --sort-order -199000 --dry-run --json
--json output: target issue, resolved update input, updated issue, verified issue, and error_category.missing_api_key, not_found, ambiguous_lookup, validation, permission_denied, and network.