@remixhq/claude-plugin 0.1.15 → 0.1.16
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/.claude-plugin/plugin.json +1 -1
- package/agents/remix-collab.md +8 -0
- package/dist/hook-post-collab.cjs +7508 -38
- package/dist/hook-post-collab.cjs.map +1 -1
- package/dist/hook-stop-collab.cjs +689 -196
- package/dist/hook-stop-collab.cjs.map +1 -1
- package/dist/hook-user-prompt.cjs +4 -3
- package/dist/hook-user-prompt.cjs.map +1 -1
- package/dist/index.js +3 -3
- package/dist/index.js.map +1 -1
- package/dist/mcp-server.cjs +1151 -347
- package/dist/mcp-server.cjs.map +1 -1
- package/package.json +3 -3
- package/skills/safe-collab-workflow/SKILL.md +9 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@remixhq/claude-plugin",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.16",
|
|
4
4
|
"description": "Claude Code plugin for Remix collaboration workflows",
|
|
5
5
|
"homepage": "https://github.com/RemixDotOne/remix-claude-plugin",
|
|
6
6
|
"license": "MIT",
|
|
@@ -31,8 +31,8 @@
|
|
|
31
31
|
"prepack": "npm run build"
|
|
32
32
|
},
|
|
33
33
|
"dependencies": {
|
|
34
|
-
"@remixhq/core": "^0.1.
|
|
35
|
-
"@remixhq/mcp": "^0.1.
|
|
34
|
+
"@remixhq/core": "^0.1.11",
|
|
35
|
+
"@remixhq/mcp": "^0.1.11"
|
|
36
36
|
},
|
|
37
37
|
"devDependencies": {
|
|
38
38
|
"@types/node": "^25.4.0",
|
|
@@ -10,6 +10,7 @@ In a Remix-bound repo, treat Remix MCP tools as the authoritative workflow layer
|
|
|
10
10
|
Canonical rules:
|
|
11
11
|
|
|
12
12
|
- In a bound repo, Remix tools are the required workflow layer for collaboration work.
|
|
13
|
+
- In a bound repo, branch switches are collaboration-state transitions because each branch can resolve to its own Remix lane and app lineage.
|
|
13
14
|
- Historical intent questions go to Remix memory before raw git history.
|
|
14
15
|
- Raw git mutation is not the normal collaboration path in a bound repo.
|
|
15
16
|
- Before the final response, you must record exactly one completed turn with `remix_collab_finalize_turn`.
|
|
@@ -36,6 +37,14 @@ Follow this order:
|
|
|
36
37
|
7. Use raw git history only after Remix memory has narrowed the relevant change, or when the user explicitly asks for exact commit, blame, ancestry, or patch-level detail.
|
|
37
38
|
8. Before the final response, call `remix_collab_finalize_turn`.
|
|
38
39
|
|
|
40
|
+
After switching branches:
|
|
41
|
+
|
|
42
|
+
1. Run `remix_collab_status`.
|
|
43
|
+
2. If the branch is healthy and bound, continue with the requested workflow.
|
|
44
|
+
3. If the branch is unbound, initialize or provision that branch lane before mutation commands.
|
|
45
|
+
4. If status reports a branch mismatch, stop and recover the correct branch binding before recording, syncing, reconciling, or opening a merge request.
|
|
46
|
+
5. Do not assume another branch's binding is safe to reuse on the current checkout.
|
|
47
|
+
|
|
39
48
|
Important rules:
|
|
40
49
|
|
|
41
50
|
- If the repo is unbound, use `remix_collab_init` for the current repo, `remix_collab_remix` for a new fork from an existing app lineage, or `remix_collab_checkout` to materialize an existing app as-is.
|