<body-file> ``` 4. **Unassign** = `linear-cli issues assign <ID>` with the user omitted. 5. **Workflow states** = `linear-cli statuses list -t <TEAM>` (there is no `teams states`). 6. **Escape hatch.** Anything the dedicated commands can't do: `linear-cli api query`/`api mutate` run raw GraphQL against the Linear API (this is why we use linear-cli — the previous CLI had no such hatch). ## Command map ```bash # Issues (alias: i) linear-cli issues get <ID> [-o json] # single issue (state is {name}; --comments adds STANDALONE comments only) linear-cli issues list --team <KEY> [--limit N] [--state X] [--assignee me] [-o json] linear-cli issues create "<title>" --team <KEY> [--state X] [-d -] # description via stdin with -d - linear-cli issues update <ID> [--state X] [--assignee me|<user>] [--priority N] [--data -] linear-cli issues assign <ID> [<user>] # omit <user> to UNASSIGN linear-cli issues comment <ID> --body - # add a comment (body via stdin) # Comments / relations / search / statuses linear-cli comments list <ID> # STANDALONE only — see gotcha #1 for anchored linear-cli relations add <BLOCKER> <BLOCKED> -r blocks # "A blocked by B" = relations add B A -r blocks (the blocked-by enum is broken on 0.3.26); also -r related|duplicate linear-cli relations parent <CHILD> <PARENT> # set parent (issues create has no --parent flag) linear-cli search issues "<query>" [--filter 'state.name=Backlog'] # workspace-wide; NO --team flag (use `issues list --team` to scope) linear-cli statuses list -t <KEY> # Projects / users / uploads linear-cli projects get|list|create ... linear-cli users list ; linear-cli whoami linear-cli uploads fetch "<uploads.linear.app URL>" -f <file> # authenticated download ``` Output flags (agent-friendly): `-o json|ndjson`, `-q` (quiet), `--id-only`, `--compact`, `--fields <a,b>`. ## In-repo helper scripts | Script | Purpose | |---|---| | `linear-context.sh <ID>` | Full issue digest **including anchored comments** (gotcha #1). | | `linear-deps-graph.sh <ID> \| --team <KEY>` | Dependency graph as `{nodes, edges}` (gotcha #2). | | `linear-create-child.sh <parent\|-> <team> <state\|-> <title> <body-file>` | Parent-linked issue create — create → `relations parent` → verify (gotcha #3). | | `linear-post.sh <comment\|description> <ID> <body-file>` | Post a comment or replace a description from a file. | | `mark-ready-for-release.sh <ID>` | Move to Ready-For-Release **and unassign**.

--- name: linear description: Linear via linear-cli — MUST READ before running Linear commands, especially for reading comments or dependencies (the obvious commands silently miss both) --- # Linear (linear-cli) — Quick Reference Linear is driven by **Finesssee `linear-cli`** (Rust; binary `linear-cli`, installed to `~/.cargo/bin`). This is a short reference for the **non-obvious** parts — for everything else use `linear-cli --help`, `linear-cli common`, or `linear-cli agent`. Auth: `linear-cli auth oauth` (browser) or `LINEAR_API_KEY`; check with `linear-cli auth status`. The full issue lifecycle is automated by the in-repo skills (`/start`, `/finish`, `/full`, `/checkpoint`, `/next`, `/quality-review`, `/prd`, `/triage`) — no install step. ## ⚠️ Gotchas that bite (read these) 1. **Anchored (inline) comments are invisible to the obvious commands.** A comment made by *highlighting text in the issue description* is stored on the description's `documentContent`, NOT on `issue.comments`. `linear-cli comments list ` and `issues get` return only standalone comments and will report "no comments" while reviewer corrections sit on the description. **To read an issue with its full comment thread, use the digest:** ```bash ~/.claude/scripts/linear-context.sh PL-13 # markdown digest: desc + deps + standalone AND anchored comments ``` Raw form (what the digest does): resolve the issue's `documentContent.id`, then `comments(filter:{documentContent:{id:{eq:}}})` via `linear-cli api query`. 2. **No dependency commands or flags.** There is no `deps` command and no `search --has-blockers/--blocked-by/--has-circular-deps`. Get the graph as `{nodes, edges}` and filter with `jq`: ```bash ~/.claude/scripts/linear-deps-graph.sh PL-13 # local graph (issue + neighbors) ~/.claude/scripts/linear-deps-graph.sh --team PL # whole-team graph (active issues) ``` Per-issue relations also exist directly: `linear-cli relations list `. 3. **`issues create` has no `--parent` flag** (and its `--data` silently drops `parentId`). Use the helper — it creates the issue, links the parent with `relations parent`, and verifies the link: ```bash ~/.claude/scripts/linear-create-child.sh

<body-file> ``` 4. **Unassign** = `linear-cli issues assign <ID>` with the user omitted. 5. **Workflow states** = `linear-cli statuses list -t <TEAM>` (there is no `teams states`). 6. **Escape hatch.** Anything the dedicated commands can't do: `linear-cli api query`/`api mutate` run raw GraphQL against the Linear API (this is why we use linear-cli — the previous CLI had no such hatch). ## Command map ```bash # Issues (alias: i) linear-cli issues get <ID> [-o json] # single issue (state is {name}; --comments adds STANDALONE comments only) linear-cli issues list --team <KEY> [--limit N] [--state X] [--assignee me] [-o json] linear-cli issues create "<title>" --team <KEY> [--state X] [-d -] # description via stdin with -d - linear-cli issues update <ID> [--state X] [--assignee me|<user>] [--priority N] [--data -] linear-cli issues assign <ID> [<user>] # omit <user> to UNASSIGN linear-cli issues comment <ID> --body - # add a comment (body via stdin) # Comments / relations / search / statuses linear-cli comments list <ID> # STANDALONE only — see gotcha #1 for anchored linear-cli relations add <BLOCKER> <BLOCKED> -r blocks # "A blocked by B" = relations add B A -r blocks (the blocked-by enum is broken on 0.3.26); also -r related|duplicate linear-cli relations parent <CHILD> <PARENT> # set parent (issues create has no --parent flag) linear-cli search issues "<query>" [--filter 'state.name=Backlog'] # workspace-wide; NO --team flag (use `issues list --team` to scope) linear-cli statuses list -t <KEY> # Projects / users / uploads linear-cli projects get|list|create ... linear-cli users list ; linear-cli whoami linear-cli uploads fetch "<uploads.linear.app URL>" -f <file> # authenticated download ``` Output flags (agent-friendly): `-o json|ndjson`, `-q` (quiet), `--id-only`, `--compact`, `--fields <a,b>`. ## In-repo helper scripts | Script | Purpose | |---|---| | `linear-context.sh <ID>` | Full issue digest **including anchored comments** (gotcha #1). | | `linear-deps-graph.sh <ID> \| --team <KEY>` | Dependency graph as `{nodes, edges}` (gotcha #2). | | `linear-create-child.sh <parent\|-> <team> <state\|-> <title> <body-file>` | Parent-linked issue create — create → `relations parent` → verify (gotcha #3). | | `linear-post.sh <comment\|description> <ID> <body-file>` | Post a comment or replace a description from a file. | | `mark-ready-for-release.sh <ID>` | Move to Ready-For-Release **and unassign**. | </article></body></html>

linear

Install this skill

Comments