mcpField
L
linear-issues

linear-issues

github.com/lwlee2608Productivity1126 installsUpdated 1d ago
Repository

About linear-issues

A skill for carrying out Linear work through the connected Linear MCP server. It sets rules for resolving IDs, confirming unrequested writes, and verifying changes.

Key features

  1. 01Uses Linear MCP tools
  2. 02Resolves names to UUIDs
  3. 03Requires confirmation for unrequested writes
  4. 04Re-reads objects after changes

Use cases

  1. 01Create or update Linear issues
  2. 02Add concise issue comments
  3. 03Verify a change and report its URL

MCP support

Requires the Linear MCP server for all Linear operations and forbids fallback to the GraphQL API or web UI. It specifies the server URL and connection setup if no server is connected.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lwlee2608/agent-skills --skill linear-issues

After installing, type/linear-issuesin Claude Code to confirm it loaded.

Details

From the project README

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.

  2. 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:

    claude mcp add --transport http linear https://mcp.linear.app/mcp

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Comments

Markdown supported