@bglocation/tune-context 1.0.0 → 1.0.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.
@@ -9,7 +9,7 @@
9
9
  "name": "tune-context",
10
10
  "source": "./",
11
11
  "description": "Context-efficiency configurator for Claude Code: doctrine skills (token-efficiency, caveman, cdd, phase-workflow) plus a tune-context configurator that scaffolds a lean CLAUDE.md, subagents, settings and hooks.",
12
- "version": "1.0.0",
12
+ "version": "1.0.1",
13
13
  "author": {
14
14
  "name": "Szymon Walczak",
15
15
  "url": "https://bglocation.dev"
@@ -2,7 +2,7 @@
2
2
  "name": "tune-context",
3
3
  "displayName": "tune-context",
4
4
  "description": "Context-efficiency configurator for Claude Code: doctrine skills (token-efficiency, caveman, cdd, phase-workflow) plus a tune-context configurator that scaffolds a lean CLAUDE.md, subagents, settings and hooks.",
5
- "version": "1.0.0",
5
+ "version": "1.0.1",
6
6
  "author": {
7
7
  "name": "Szymon Walczak",
8
8
  "url": "https://bglocation.dev"
package/README.md CHANGED
@@ -49,12 +49,15 @@ tune-context init # in any repo
49
49
  Prefer the model-driven path? Install the plugin and use the skill — it does the
50
50
  same thing plus wiki wiring and richer MCP detection:
51
51
 
52
- ```bash
53
- claude --plugin-dir "$(npm root -g)/@bglocation/tune-context" # global install
54
- # then, inside a session in the repo you want to configure:
55
- /tune-context
52
+ ```text
53
+ /plugin marketplace add https://gitlab.com/bglocation/tune-context.git
54
+ /plugin install tune-context@bglocation
55
+ /reload-plugins
56
56
  ```
57
57
 
58
+ Then run `/tune-context` in the repo you want to configure. (The `.git` suffix
59
+ matters — see [Install & run](#install--run).)
60
+
58
61
  The section below breaks down all three entry points and when to use each.
59
62
 
60
63
  ## Install & run
@@ -85,10 +88,16 @@ in every session. The best UX is the **marketplace** — install once, get updat
85
88
  with `/plugin marketplace update`:
86
89
 
87
90
  ```text
88
- /plugin marketplace add https://gitlab.com/bglocation/tune-context
91
+ /plugin marketplace add https://gitlab.com/bglocation/tune-context.git
89
92
  /plugin install tune-context@bglocation
90
93
  ```
91
94
 
95
+ The **`.git` suffix is required**: without it Claude Code treats the URL as a
96
+ direct link to a hosted `marketplace.json` instead of cloning the repo, and the
97
+ add fails with `Invalid marketplace schema`. Same commands work non-interactively
98
+ as `claude plugin marketplace add …` / `claude plugin install …` — useful where
99
+ the `/plugin` panel isn't available (e.g. the VS Code extension).
100
+
92
101
  Or point Claude at a directory directly (no marketplace):
93
102
 
94
103
  ```bash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bglocation/tune-context",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "description": "Context-efficiency configurator for Claude Code — token-saving doctrine packaged as skills, plus a tune-context configurator that scaffolds a lean CLAUDE.md, doctrine skills, subagents, settings, hooks and MCP wiring.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -36,8 +36,9 @@
36
36
  ],
37
37
  "scripts": {
38
38
  "verify:pack": "node scripts/verify-pack.mjs",
39
+ "verify:plugin": "node scripts/verify-plugin.mjs",
39
40
  "smoke:init": "node scripts/smoke-init.mjs",
40
- "prepublishOnly": "npm run verify:pack && npm run smoke:init"
41
+ "prepublishOnly": "npm run verify:pack && npm run verify:plugin && npm run smoke:init"
41
42
  },
42
43
  "publishConfig": {
43
44
  "access": "public"