@remixhq/claude-plugin 0.1.4 → 0.1.5

package/.claude-plugin/marketplace.json

@@ -13,7 +13,7 @@
       "source": {
         "source": "npm",
         "package": "@remixhq/claude-plugin",
-        "version": "^0.1.0"
+        "version": "0.1.5"
       },
       "homepage": "https://github.com/RemixDotOne/remix-claude-plugin",
       "repository": "https://github.com/RemixDotOne/remix-claude-plugin",

package/.claude-plugin/plugin.json

@@ -1,11 +1,12 @@
 {
   "name": "remix",
   "description": "Remix collaboration workflows for Claude Code",
-  "version": "0.1.0",
+  "version": "0.1.5",
   "author": {
     "name": "Remix"
   },
   "license": "MIT",
+  "homepage": "https://github.com/RemixDotOne/remix-claude-plugin",
   "repository": "https://github.com/RemixDotOne/remix-claude-plugin",
   "skills": [
     "./skills/safe-collab-workflow/SKILL.md",

package/agents/remix-collab.md

@@ -32,6 +32,7 @@ When appropriate:
 
 - use `remix_collab_init` to bind the current repo
 - use `remix_collab_remix` to start from an existing app lineage
+- use `remix_collab_checkout` to continue work on an existing app id without creating a fork
 - use memory summary/search/timeline tools before repo inspection when historical context or reasoning is needed
 - use the explicit change-step diff tool only after you already know which `changeStepId` matters
 - use `remix_collab_add` only when a manual changed-turn recording step is explicitly needed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remixhq/claude-plugin",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Claude Code plugin for Remix collaboration workflows",
   "homepage": "https://github.com/RemixDotOne/remix-claude-plugin",
   "license": "MIT",
@@ -31,8 +31,8 @@
     "prepack": "npm run build"
   },
   "dependencies": {
-    "@remixhq/core": "^0.1.6",
-    "@remixhq/mcp": "^0.1.6"
+    "@remixhq/core": "^0.1.7",
+    "@remixhq/mcp": "^0.1.7"
   },
   "devDependencies": {
     "@types/node": "^25.4.0",

package/skills/init-or-remix/SKILL.md

@@ -3,32 +3,37 @@ name: init-or-remix
 description: Use when deciding whether to bind the current repo to Remix or create a new remix checkout from an existing app.
 ---
 
-# Init Or Remix
+# Init, Remix, Or Checkout
 
-Use this skill when onboarding a repository into Remix or starting work from an existing Remix app lineage.
+Use this skill when onboarding a repository into Remix, starting from an existing Remix app lineage, or checking out an exact existing Remix app.
 
 This is the entry-point choice:
 
 - use init when the current repository should become the bound Remix repo,
-- use remix when work should start from an existing Remix app lineage in a fresh checkout.
+- use remix when work should start from an existing Remix app lineage in a fresh fork checkout,
+- use checkout when the exact existing app should be materialized locally without creating a new fork.
 
 Decision rule:
 
 - Use `remix_collab_init` when the user wants to bind the current local repository to Remix.
 - Use `remix_collab_remix` when the user wants a new local checkout forked from an existing Remix app.
+- Use `remix_collab_checkout` when the user wants the exact existing app checked out locally as-is.
 
 Recommended sequence:
 
 1. If the current repo may already be bound, use `remix_collab_status` first.
 2. If the task is about the current local repo and it is unbound, prefer `remix_collab_init`.
-3. If the task starts from an existing app id, prefer `remix_collab_remix`.
-4. After init or remix, use `remix_collab_status` in the resulting repo to inspect readiness.
+3. If the task starts from an existing app id and the user wants a new fork, prefer `remix_collab_remix`.
+4. If the task starts from an existing app id and the user wants the same app id locally, prefer `remix_collab_checkout`.
+5. After init, remix, or checkout, use `remix_collab_status` in the resulting repo to inspect readiness.
 
 Important note:
 
 - `remix_collab_init` is a repo-level, history-preserving bind of the current git repository.
 - Do not treat init as a subdirectory import workflow.
 - `remix_collab_remix` creates a new bound checkout in a newly created directory under the provided or current working directory.
+- `remix_collab_checkout` creates a new bound checkout for the exact existing app id without creating a new fork.
 - Do not treat remix as binding the current repository in place.
-- If the user wants to start from an existing Remix app lineage instead, use `remix_collab_remix`.
-- After init or remix, the bound repo is eligible for automatic end-of-response turn recording in this plugin setup.
+- If the user wants to start from an existing Remix app lineage with a new fork, use `remix_collab_remix`.
+- If the user wants to continue work on the same existing app id, use `remix_collab_checkout`.
+- After init, remix, or checkout, the bound repo is eligible for automatic end-of-response turn recording in this plugin setup.

package/skills/safe-collab-workflow/SKILL.md

@@ -45,7 +45,7 @@ Follow this order:
 
 Important rules:
 
-- If the repo is unbound, use `remix_collab_init` for the current repo or `remix_collab_remix` for an existing Remix app lineage.
+- 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.
 - In a bound repo, do not use raw git `commit`, `push`, `pull`, `merge`, `rebase`, or `reset` for ordinary Remix collaboration work.
 - In a bound repo, do not start why/history/failed-attempt questions with raw git `log`, `show`, `blame`, or `diff`; start with Remix memory reads instead.
 - Do not manually fire per-turn recording calls during ordinary work. The end-of-response hook records one turn once per completed assistant response.