@kyaukyuai/linear-cli 2.12.0 → 2.12.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,20 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [2.12.1] - 2026-03-30
6
+
7
+ ### Added
8
+
9
+ - added `stateName` to `issue list --json` as an additive convenience field while keeping the nested `state` object unchanged
10
+
11
+ ### Changed
12
+
13
+ - refreshed the README, agent workflow docs, and skills.sh install guidance to better position `linear-cli` as an agent-first Linear CLI
14
+
15
+ ### Fixed
16
+
17
+ - preserved agent-first generated skill docs so `deno task generate-skill-docs` no longer reverts the published skill description and command guidance
18
+
5
19
  ## [2.12.0] - 2026-03-30
6
20
 
7
21
  ### Added
package/README.md CHANGED
@@ -16,6 +16,22 @@ linear notification list --json
16
16
 
17
17
  interactive commands still exist for humans, but the primary design goal is that an agent can discover commands incrementally, pass all important input as flags or stdin, and get machine-readable success or failure back.
18
18
 
19
+ ## for agents
20
+
21
+ If an agent only reads one page, it should be this README plus the two contract docs below.
22
+
23
+ - start with `linear capabilities --json` to discover which commands support `--json`, `--dry-run`, stdin, confirmation bypass, and stable automation contracts
24
+ - prefer stable read surfaces such as `issue`, `project`, `cycle`, `milestone`, `document`, `webhook`, `notification`, `team`, `user`, `workflow-state`, `label`, `initiative`, and update feeds with `--json`
25
+ - preview writes with `--dry-run --json` before mutating Linear
26
+ - apply writes with `--json`, then inspect exit codes and `error.details` instead of parsing terminal text
27
+ - use stdin or file flags for Markdown-heavy descriptions and comments instead of long inline shell strings
28
+
29
+ Recommended docs:
30
+
31
+ - [Agent workflow guide](docs/agent-first.md)
32
+ - [Automation contracts](docs/json-contracts.md)
33
+ - [stdin and pipeline policy](docs/stdin-policy.md)
34
+
19
35
  ## screencast demos
20
36
 
21
37
  <details>
@@ -36,6 +52,24 @@ interactive commands still exist for humans, but the primary design goal is that
36
52
 
37
53
  for agents and scripts, prefer a pinned install in the repo or runtime you control.
38
54
 
55
+ ### install as a skill
56
+
57
+ If you want to expose `linear-cli` as a reusable skill on top of an existing agent runtime, install it from the repo root and select the public skill explicitly:
58
+
59
+ ```bash
60
+ npx skills add https://github.com/kyaukyuai/linear-cli --skill linear-cli
61
+ ```
62
+
63
+ This is the most compatible form for `skills` and `skills.sh`.
64
+
65
+ If you want to point directly at the skill directory instead, this also works:
66
+
67
+ ```bash
68
+ npx skills add https://github.com/kyaukyuai/linear-cli/tree/main/skills/linear-cli
69
+ ```
70
+
71
+ Once installed, agents can load the skill and then call the local `linear` binary using the agent-first guidance in [skills/linear-cli/SKILL.md](skills/linear-cli/SKILL.md).
72
+
39
73
  ### npm / bun / pnpm
40
74
 
41
75
  install as a dependency to pin a version in your project:
@@ -59,6 +93,8 @@ bunx linear issue list
59
93
 
60
94
  package on npm: [@kyaukyuai/linear-cli](https://www.npmjs.com/package/@kyaukyuai/linear-cli)
61
95
 
96
+ skills directory on GitHub: [skills/linear-cli](https://github.com/kyaukyuai/linear-cli/tree/main/skills/linear-cli)
97
+
62
98
  ### deno via jsr
63
99
 
64
100
  ```bash
@@ -106,6 +142,15 @@ compared to upstream, this fork adds and maintains capabilities aimed at automat
106
142
  - workspace-aware auth management with keyring migration and default workspace support
107
143
  - generated AI-agent skill docs, Claude plugin metadata, npm publishing, and Homebrew tap release plumbing
108
144
 
145
+ ## docs map
146
+
147
+ Use the docs in this order if you are building an agent integration:
148
+
149
+ 1. [docs/agent-first.md](docs/agent-first.md) for the recommended discover/read/preview/apply/recover loop
150
+ 2. [docs/json-contracts.md](docs/json-contracts.md) for stable JSON payloads, exit codes, timeout semantics, and dry-run envelopes
151
+ 3. [docs/stdin-policy.md](docs/stdin-policy.md) for pipeline and file-input conventions
152
+ 4. [`linear capabilities --json`](#automation-contract) for machine-readable command metadata at runtime
153
+
109
154
  ## automation contract
110
155
 
111
156
  for bot and org-wide automation use cases, `linear-cli` defines a stable JSON contract for a focused automation tier.
@@ -23,7 +23,7 @@
23
23
  "hasInstallScript": true,
24
24
  "license": "MIT",
25
25
  "name": "@kyaukyuai/linear-cli",
26
- "version": "2.12.0"
26
+ "version": "2.12.1"
27
27
  },
28
28
  "node_modules/@isaacs/cliui": {
29
29
  "engines": {
@@ -542,5 +542,5 @@
542
542
  }
543
543
  },
544
544
  "requires": true,
545
- "version": "2.12.0"
545
+ "version": "2.12.1"
546
546
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "artifactDownloadUrls": [
3
- "https://github.com/kyaukyuai/linear-cli/releases/download/v2.12.0"
3
+ "https://github.com/kyaukyuai/linear-cli/releases/download/v2.12.1"
4
4
  ],
5
5
  "bin": {
6
6
  "linear": "run-linear.js"
@@ -85,7 +85,7 @@
85
85
  "zipExt": ".tar.xz"
86
86
  }
87
87
  },
88
- "version": "2.12.0",
88
+ "version": "2.12.1",
89
89
  "volta": {
90
90
  "node": "18.14.1",
91
91
  "npm": "9.5.0"