# Linear Ticket

> Use this skill whenever the user shares a Linear.app ticket link or ticket ID (e.g. FLX-123, https://linear.app/…/issue/FLX-123/…). Fetch and deeply read the full ticket — description, status, assignee, all comments and replies — before doing any work. Raise concerns if the user's request conflicts with or diverges from what the ticket actually describes.

- Skill: `sakydev/linear-ticket` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sakydev/linear-ticket`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sakydev/linear-ticket/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sakydev (https://skillmd.com/u/sakydev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sakydev/linear-ticket

---


# Linear Ticket Skill

## Step 1 — Get the ticket ID

Parse it from whatever was given.

| Input | Extracted |
|---|---|
| `FLX-123` | `FLX-123` |
| `https://linear.app/fluxend/issue/FLX-123/some-title` | `FLX-123` |

## Step 2 — Read everything

Do not skip a step.

1. **`mcp__linear-server__get_issue`** - title, description, status, priority, assignee, labels, parent, project.
2. **`mcp__linear-server__list_comments`** - every comment, every reply. Read them all. Replies often override the description.
3. **`mcp__linear-server__get_project`** - if the ticket belongs to a project.
4. **`mcp__linear-server__get_issue`** on the parent - if one exists.

## Step 3 — Understand before acting

Build a clear picture of:

- What the ticket asks for.
- What comments changed or decided.
- Current status.
- Who owns it.

## Step 4 — Raise concerns first

Check the user's request against what you read. Speak up before writing a single line of code.

| Situation | Say |
|---|---|
| Ticket is Done or Cancelled | "This ticket is already [status]. Sure you want this?" |
| Request contradicts the ticket | "Ticket says X. You're asking for Y. Which one?" |
| Request is narrower than ticket | Say what you're not doing. Confirm that's fine. |
| Request is broader than ticket | "You're asking for Z. That's outside FLX-123. Include it or stay scoped?" |
| Comment overrides description | "Per [author] on [date], approach changed to X. Following that unless you say otherwise." |
| Ticket is vague | Ask the one most important question. Just one. |

Nothing looks wrong? Proceed without comment. No "ticket looks good" preamble.

## Step 5 — Work

Do what was asked with full ticket context in your head.