@skitterbyte/skitterspec-linear 15.0.0 → 17.1.0
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/MIGRATION.md +218 -0
- package/README.md +37 -1
- package/assets/claude-md-section.md +42 -18
- package/assets/commands/allow-main.md +33 -0
- package/assets/commands/spec-remote-review.md +22 -0
- package/assets/commands/spec-skip.md +24 -0
- package/assets/core/SETUP.md +10 -6
- package/assets/core/env.config.json.example +6 -3
- package/assets/core/env.config.md +183 -25
- package/assets/core/linear.config.json.example +2 -1
- package/assets/core/linear.config.md +49 -22
- package/assets/hooks/main-guard.cjs +145 -0
- package/assets/hooks/review-gate.cjs +8 -3
- package/assets/review/page.html +1174 -101
- package/assets/rules/commit-trailers.md +17 -7
- package/assets/rules/offered-unblocks.md +100 -0
- package/assets/rules/spec-planning.md +195 -14
- package/assets/rules/spec-reports.md +181 -29
- package/assets/skills/no-spec/SKILL.md +219 -0
- package/assets/skills/spec/SKILL.md +277 -21
- package/assets/skills/spec-bug/SKILL.md +73 -30
- package/assets/skills/spec-cancel/SKILL.md +31 -2
- package/assets/skills/spec-claim/SKILL.md +12 -4
- package/assets/skills/spec-complete/SKILL.md +27 -2
- package/assets/skills/spec-diff/SKILL.md +164 -37
- package/assets/skills/spec-hotfix/SKILL.md +61 -25
- package/assets/skills/spec-init/SKILL.md +4 -2
- package/assets/skills/spec-linear-setup/SKILL.md +19 -11
- package/assets/skills/spec-next/SKILL.md +168 -60
- package/assets/skills/spec-push/SKILL.md +45 -0
- package/assets/skills/spec-review/SKILL.md +89 -2
- package/assets/skills/spec-reviewed/SKILL.md +31 -5
- package/assets/skills/spec-start/SKILL.md +40 -3
- package/assets/skills/spec-status/SKILL.md +20 -6
- package/assets/skills/spec-sync/SKILL.md +1 -0
- package/package.json +2 -2
- package/src/cli.js +1612 -172
- package/src/env/classify.js +87 -2
- package/src/env/config.js +333 -19
- package/src/env/hooks.js +102 -33
- package/src/env/live.js +124 -1
- package/src/env/mainguard.js +240 -0
- package/src/env/provision.js +106 -10
- package/src/env/registry.js +70 -6
- package/src/env/resolve.js +128 -5
- package/src/env/review.js +854 -29
- package/src/env/reviewers/coderabbit.js +228 -0
- package/src/env/reviewers.js +517 -0
- package/src/env/serve.js +474 -50
- package/src/env/supervise.js +8 -1
- package/src/env/teardown.js +12 -1
- package/src/init.js +185 -24
- package/src/vendor/linear/api.js +111 -2
- package/src/vendor/linear/cli-sync.js +661 -11
- package/src/vendor/linear/config.js +41 -13
- package/src/vendor/linear/doctor.js +6 -5
- package/src/vendor/sync-core/index.js +11 -3
- package/src/vendor/sync-core/src/compare.js +65 -0
- package/src/vendor/sync-core/src/normalize.js +26 -0
|
@@ -33,9 +33,20 @@ Use the argument, else the spec in context; ask if unclear.
|
|
|
33
33
|
## 2. Fetch the Linear issue (optional, for drift)
|
|
34
34
|
|
|
35
35
|
If the spec has a `linear_identifier`, discover the Linear MCP read tool
|
|
36
|
-
(`get_issue`) and write the issue JSON to a temp file
|
|
37
|
-
|
|
38
|
-
|
|
36
|
+
(`get_issue`) and write the issue JSON to a temp file. If Linear isn't connected,
|
|
37
|
+
skip the drift lines (still report pending-push).
|
|
38
|
+
|
|
39
|
+
**Write the whole issue, including its `description`.** The engine reports two
|
|
40
|
+
independent kinds of drift off that one file: the workflow-state someone moved,
|
|
41
|
+
and the **description someone edited**. Write only the state fields and the
|
|
42
|
+
second check has nothing to look at — and it says nothing rather than guessing,
|
|
43
|
+
so the loss is silent. Keep `url` too: it is what the description line points
|
|
44
|
+
the reader at.
|
|
45
|
+
|
|
46
|
+
**The description itself never enters the conversation.** The engine hashes it
|
|
47
|
+
and compares hashes; what it prints is *that* the text changed, plus where to
|
|
48
|
+
read it. Do not open the temp file, and do not paste the description into your
|
|
49
|
+
report.
|
|
39
50
|
|
|
40
51
|
Optionally fetch the workspace issue-state names to a file to validate the
|
|
41
52
|
configured `states` at the same time.
|
|
@@ -81,9 +92,12 @@ the shape; this section carries only what is specific here.
|
|
|
81
92
|
**Verdicts**
|
|
82
93
|
|
|
83
94
|
- `✅` — in sync; nothing would push.
|
|
84
|
-
- `⚠️` — drift: N objects would push,
|
|
85
|
-
|
|
86
|
-
reason someone
|
|
95
|
+
- `⚠️` — drift: N objects would push, Linear's workflow state was moved by hand,
|
|
96
|
+
or the issue's **description** was edited on Linear since the last push. None
|
|
97
|
+
is an error — the repo wins on the next push — but all are the reason someone
|
|
98
|
+
ran this. **Say which**, since the three call for different things: a pending
|
|
99
|
+
push is routine, a moved state is usually someone else's automation, and an
|
|
100
|
+
edited description means a person wrote something that the next push replaces.
|
|
87
101
|
- `⏸` — no config, or the spec is not linked. Nothing to compare.
|
|
88
102
|
|
|
89
103
|
**Fields:** `Tracker` · `Follow-ups` · `Next`
|
|
@@ -42,6 +42,7 @@ In a project that installs the Linear superset the binary is
|
|
|
42
42
|
| "what specs are there?", "what's in the backlog?", "what is Jane on?" | `list` — or hand to `/spec-list` |
|
|
43
43
|
| "did the mirror survive the push?" | `verify <spec> --stored <file>` |
|
|
44
44
|
| "link this spec to KEY-1 by hand" | `stamp <spec> --issue KEY-1` |
|
|
45
|
+
| "this spec lost its link", "a push made a duplicate issue" | `reattach <spec>` — or `--to KEY-1` to name one |
|
|
45
46
|
| "mirror the whole backlog / every complete spec" | `apply --all <bucket>` — **confirm first** |
|
|
46
47
|
| "is the team key stale?", "did Linear get renamed?" | `retarget` |
|
|
47
48
|
| "what ticket am I on?", writing a commit | `ref` |
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@skitterbyte/skitterspec-linear",
|
|
3
|
-
"version": "
|
|
4
|
-
"description": "Spec-driven development for Claude Code, with one-way Linear sync
|
|
3
|
+
"version": "17.1.0",
|
|
4
|
+
"description": "Spec-driven development for Claude Code, with one-way Linear sync — a superset of @skitterbyte/skitterspec: the base filesystem workflow plus /spec-status · /spec-push and the spec-sync CLI. The repo is canonical; Linear is a generated mirror. Install this OR the base, not both.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"claude",
|
|
7
7
|
"claude-code",
|