lwlee2608/agent-skills

linear-issues

Use when reading, searching, creating, updating, or commenting on Linear issues.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/lwlee2608/agent-skills --skill linear-issues

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Work with Linear

Do all Linear work through the installed Linear MCP server.

Rules

  1. Use the Linear MCP tools (mcp__linear__*: list_issues, get_issue, create_issue, update_issue, list_comments, create_comment, …). Read the actual schemas before calling — Linear renames tools without notice.
  1. Never fall back to the GraphQL API or web UI. If no Linear MCP server is connected, stop and tell the user to add https://mcp.linear.app/mcp (HTTP transport) to their agent. In Claude Code:
bash
   claude mcp add --transport http linear https://mcp.linear.app/mcp
  1. Resolve names to IDs before writing. Team, state, label, and assignee fields take UUIDs; a display name fails or silently no-ops. Call the matching list_* tool first.
  1. Keep comments short. 1–3 sentences. Outcome first, link the PR instead of pasting the diff, no preamble, no recap of the ticket, no sign-off, no emoji.
   Root cause: config loader reads `retry_count` but the YAML key is `retryCount`, so it binds 0. Fixed in #482.
  1. Don't hand-move a PR-linked issue to Done. A linked PR (branch name, or Fixes ENG-482 in the title/body) moves the issue to Done on merge. Set it by hand only when no PR is linked, or the user asks.
  1. Confirm before writes the user did not ask for. Issues, status changes, and comments are visible to the whole team. If they asked for the write, just do it.

Verification

  1. Re-read the object after a write; report the identifier and URL (ENG-482 — https://linear.app/…).
  2. If a comment runs past ~3 sentences, cut it.
来自同一仓库

更多 Skills

全部 Skills