@ramon-sg/issue-flow 0.2.6 → 0.2.7

package/README.md

@@ -2,7 +2,7 @@
 
 Flujo de trabajo de issue a PR para cualquier repo, en local y en las sesiones de Claude en la nube: nombra la rama de cada issue, crea su worktree con puertos y Docker propios, abre el PR en draft y limpia cuando se mergea. Trae las skills que usan ese flujo.
 
-> **Instalar en un repo:** `npx agent-kitchen`, que instala este flujo con sus skills, las skills generales, `claude-cloud` y `claude-repo-guard`, y los actualiza ([agent-kitchen](https://github.com/ramon-sg/agent-kitchen)). El paquete es `@ramon-sg/issue-flow` y el comando, `issue-flow`; sin el scope, `issue-flow` en npm es otro paquete.
+> **Instalar en un repo:** `npx agent-kitchen apply`, que instala este flujo con sus skills, las skills generales, `claude-cloud` y `claude-repo-guard`, y los actualiza ([agent-kitchen](https://github.com/ramon-sg/agent-kitchen)). El paquete es `@ramon-sg/issue-flow` y el comando, `issue-flow`; sin el scope, `issue-flow` en npm es otro paquete.
 
 ## Qué va a tener
 
@@ -183,7 +183,7 @@ Es el hook `SessionStart` de Claude Code. Lo que imprime le llega a Claude como
 
 ## Lo que el flujo deja en el repo: `issue-flow init`
 
-`npx agent-kitchen` corre estos tres comandos en la versión que corresponde. Correrlos a mano sirve para probar el flujo en un repo sin lo demás.
+`npx agent-kitchen apply` corre estos tres comandos en la versión que corresponde. Correrlos a mano sirve para probar el flujo en un repo sin lo demás.
 
 ```sh
 npx @ramon-sg/issue-flow init           # pregunta cada receta y pide el OK
@@ -200,7 +200,7 @@ npx @ramon-sg/issue-flow@<versión> upgrade  # mueve el repo a esa versión (--d
 
 **`doctor`** no cambia nada. Revisa la config, las dependencias y que los hooks estén en esta versión. Cada problema dice qué lo arregla.
 
-**`upgrade`** mueve el repo a la versión que corre: las dependencias a las que fija, los hooks y el `$schema`. No consulta npm, así que se corre con la versión: `npx @ramon-sg/issue-flow@<versión> upgrade`. Nunca baja de versión: si el repo ya tiene una más nueva (por ejemplo, una copia local vieja en `node_modules`), se detiene y dice qué correr. Las skills del flujo llaman a la CLI, así que tienen que ir a la misma tag: `agent-kitchen` las mueve después. `--dry-run` solo dice qué cambiaría.
+**`upgrade`** mueve el repo a la versión que corre: `@ramon-sg/issue-flow`, los hooks y el `$schema`. `github-rest` y `skills-manager` solo suben si no llegan a la versión con que se probó issue-flow: una versión igual o más nueva, un rango que la permite (`^1.2.0` para 1.3.0, no `^0.1.0` para 0.3.0) o una fuente como `workspace:*` se deja como está y se avisa (`kept …`). No consulta npm, así que se corre con la versión: `npx @ramon-sg/issue-flow@<versión> upgrade`. Nunca baja de versión: si el repo ya tiene una más nueva (por ejemplo, una copia local vieja en `node_modules`), se detiene y dice qué correr. Las skills del flujo llaman a la CLI, así que tienen que ir a la misma tag: `agent-kitchen` las mueve después. `--dry-run` solo dice qué cambiaría.
 
 ### Recetas
 

package/dist/commands/doctor.js

@@ -11,7 +11,7 @@ import { dependencyVersion } from "../package-edits.js";
 import { hookVersions } from "../settings-hooks.js";
 import { ownVersions, PACKAGE, readJson, SETTINGS_FILE, SetupError } from "../setup-files.js";
 /** What fixes every problem: it runs init or upgrade at the right version. */
-const RUN_AGENT_KITCHEN = "run npx agent-kitchen";
+const RUN_AGENT_KITCHEN = "run npx agent-kitchen apply";
 /**
  * Checks the config.
  * @param root - The repo.

package/dist/commands/init.js

@@ -11,7 +11,7 @@ import { CONFIG_PATH, isObject } from "../config-base.js";
 import { parseConfig } from "../config.js";
 import { checkoutRoot, locateRepo } from "../git.js";
 import { UsageError, warn } from "../output.js";
-import { withFlowPackages } from "../package-edits.js";
+import { KEPT, withFlowPackages } from "../package-edits.js";
 import { applyRecipe, detectedRecipes, loadRecipes, projectPrefix } from "../recipes.js";
 import { registerHooks } from "../settings-hooks.js";
 import { FLOW_REPO, ownVersions, packageManager, readJson, SETTINGS_FILE, SetupError, writeJson } from "../setup-files.js";
@@ -68,8 +68,6 @@ async function pickRecipes(root, options, out) {
             picked.push(recipe);
     return picked;
 }
-/** How a line of a change that keeps what the repo had starts. */
-const KEPT = "kept ";
 /**
  * What `init` would write: the config, `package.json` and the settings' hooks.
  * @param root - The repo.

package/dist/commands/upgrade.d.ts

@@ -1,4 +1,4 @@
-import type { Output } from "../output.js";
+import { type Output } from "../output.js";
 /** Options of `issue-flow upgrade`. */
 export interface UpgradeOptions {
     cwd: string;

package/dist/commands/upgrade.js

@@ -1,36 +1,19 @@
 /**
  * @file `issue-flow upgrade [--dry-run]`: moves the repo's flow files to the version that
- * runs: the dev dependencies to the ones it pins, and the hooks and the config's schema to
- * it. `agent-kitchen` runs it as `npx @ramon-sg/issue-flow@<version> upgrade` and then
+ * runs: `@ramon-sg/issue-flow`, the hooks and the config's schema to it, and `github-rest`
+ * and `skills-manager` up to the versions it was tested with only if they fall short (a
+ * newer one, or a range that allows it, is kept and reported). `agent-kitchen` runs it as `npx @ramon-sg/issue-flow@<version> upgrade` and then
  * moves the flow's skills to the same tag, because the skills call this CLI.
  */
 import { CONFIG_PATH } from "../config-base.js";
 import { checkoutRoot, locateRepo } from "../git.js";
-import { dependencyVersion, withFlowPackages } from "../package-edits.js";
+import { warn } from "../output.js";
+import { dependencyVersion, isNewer, KEPT, withFlowPackages } from "../package-edits.js";
 import { hookVersions, registerHooks } from "../settings-hooks.js";
 import { FLOW_REPO, ownVersions, PACKAGE, packageManager, readJson, SETTINGS_FILE, SetupError, writeJson } from "../setup-files.js";
 import { schemaUrl } from "./init.js";
 /** The start of the schema URL `init` writes, at any version. */
 const SCHEMA_PREFIX = `https://raw.githubusercontent.com/${FLOW_REPO}/`;
-/** A release version, after an optional range sign. */
-const RELEASE = /^[\^~=]?(\d+)\.(\d+)\.(\d+)$/;
-/**
- * Whether a version is newer than another; false if either is not a release.
- * @param version - The version, maybe with a range sign.
- * @param than - The other.
- * @returns True if it is newer.
- */
-function isNewer(version, than) {
-    const [left, right] = [RELEASE.exec(version), RELEASE.exec(than)];
-    if (left === null || right === null)
-        return false;
-    for (let index = 1; index <= 3; index += 1) {
-        const diff = Number(left[index]) - Number(right[index]);
-        if (diff !== 0)
-            return diff > 0;
-    }
-    return false;
-}
 /**
  * The newest version of the flow the repo already has, in package.json or a hook.
  * @param root - The repo.
@@ -59,13 +42,17 @@ export function upgrade(options, out) {
     const versions = ownVersions();
     const current = repoVersion(root);
     if (current !== null && isNewer(current, versions.issueFlow))
-        throw new SetupError(`the repo is at issue-flow ${current}, newer than this ${versions.issueFlow}; run 'npx ${PACKAGE}@${current.replace(/^[\^~=]/, "")} upgrade' or 'npx agent-kitchen'.`);
+        throw new SetupError(`the repo is at issue-flow ${current}, newer than this ${versions.issueFlow}; run 'npx ${PACKAGE}@${current.replace(/^[\^~=]/, "")} upgrade' or 'npx agent-kitchen apply'.`);
     const writes = [];
     const lines = [];
     const pkg = withFlowPackages(readJson(root, "package.json"), versions, true);
-    if (pkg.changes.length > 0)
+    const kept = pkg.changes.filter((change) => change.startsWith(KEPT));
+    const moved = pkg.changes.filter((change) => !change.startsWith(KEPT));
+    for (const change of kept)
+        warn(out, `package.json: ${change}`);
+    if (moved.length > 0)
         writes.push({ path: "package.json", value: pkg.pkg });
-    lines.push(...pkg.changes.map((change) => `package.json: ${change}`));
+    lines.push(...moved.map((change) => `package.json: ${change}`));
     const hooks = registerHooks(readJson(root, SETTINGS_FILE), versions.issueFlow);
     if (hooks.changes.length > 0)
         writes.push({ path: SETTINGS_FILE, value: hooks.settings });

package/dist/package-edits.d.ts

@@ -2,16 +2,46 @@
  * @file The repo's `package.json` as the flow needs it: `issue-flow`, `github-rest` and
  * `skills-manager` as exact dev dependencies (the skills call them with `npx`, which then
  * uses the repo's copy), and the scripts to start an issue, prune worktrees and review a PR.
- * A dependency or script the repo already has with another value stays as it is.
+ * A dependency or script the repo already has with another value stays as it is, except
+ * that `upgrade` moves `issue-flow` to the version that runs and raises the other two only
+ * when they fall short of it: a newer version or a range that allows it is never moved back.
  */
-import type { OwnVersions } from "./setup-files.js";
+import { type OwnVersions } from "./setup-files.js";
 /**
- * The dependencies the flow pins, with their versions.
+ * Whether a version is newer than another; false if either is not a version. A leading
+ * range sign is dropped, so `^0.3.0` reads as 0.3.0.
+ * @param version - The version, maybe with a range sign.
+ * @param than - The other.
+ * @returns True if it is newer.
+ * @example isNewer("1.10.0", "1.9.0") // true
+ */
+export declare function isNewer(version: string, than: string): boolean;
+/**
+ * Whether the repo's version of a package reaches the one the flow was tested with, so
+ * `upgrade` keeps it: an exact version as new or newer, a range that allows it or newer
+ * (`^1.2.0` for 1.3.0, not `^0.1.0` for 0.3.0), or a source it cannot read (`workspace:*`,
+ * `github:…`, `latest`), which the repo chose on purpose.
+ * @param current - The repo's version or range.
+ * @param tested - The version the flow was tested with.
+ * @returns True to keep it.
+ * @example reaches("1.3.0", "1.2.0") // true
+ */
+export declare function reaches(current: string, tested: string): boolean;
+/** A dependency the flow pins: its version, and whether `upgrade` keeps one that reaches it. */
+interface Pin {
+    version: string;
+    keepsReaching: boolean;
+}
+/** How a change that keeps what the repo had starts. */
+export declare const KEPT = "kept ";
+/**
+ * The dependencies the flow pins, with their versions. `issue-flow` always follows the
+ * version that runs; the other two are a floor, so `upgrade` keeps what reaches it.
  * @param versions - This package's versions.
- * @returns Package to version.
- * @example pinnedPackages(versions)["@ramon-sg/issue-flow"] // "0.1.0"
+ * @returns Package to pin.
+ * @example pinnedPackages(versions)["@ramon-sg/issue-flow"].version // "0.1.0"
  */
-export declare function pinnedPackages(versions: OwnVersions): Record<string, string>;
+export declare function pinnedPackages(versions: OwnVersions): Record<string, Pin>;
 /**
  * The version of a package in the repo, as a dependency or a dev dependency.
  * @param pkg - The package.json.
@@ -33,3 +63,4 @@ export declare function withFlowPackages(pkg: Record<string, unknown> | null, ve
     pkg: Record<string, unknown>;
     changes: string[];
 };
+export {};

package/dist/package-edits.js

@@ -1,3 +1,103 @@
+/**
+ * @file The repo's `package.json` as the flow needs it: `issue-flow`, `github-rest` and
+ * `skills-manager` as exact dev dependencies (the skills call them with `npx`, which then
+ * uses the repo's copy), and the scripts to start an issue, prune worktrees and review a PR.
+ * A dependency or script the repo already has with another value stays as it is, except
+ * that `upgrade` moves `issue-flow` to the version that runs and raises the other two only
+ * when they fall short of it: a newer version or a range that allows it is never moved back.
+ */
+import { PACKAGE } from "./setup-files.js";
+/** A version: X.Y.Z, with an optional pre-release and build. */
+const VERSION = /^(\d+)\.(\d+)\.(\d+)(?:-([0-9A-Za-z.-]+))?(?:\+[0-9A-Za-z.-]+)?$/;
+/** A range this file understands: a sign (`^`, `~`, `>=`, `=`) before a version. */
+const SIMPLE_RANGE = /^(\^|~|>=|=)\s*(\S+)$/;
+/**
+ * Parses a version.
+ * @param text - The version, without a range sign.
+ * @returns It, or null if it is not one.
+ */
+function parse(text) {
+    const match = VERSION.exec(text);
+    if (match === null)
+        return null;
+    return { parts: [Number(match[1]), Number(match[2]), Number(match[3])], pre: match[4] ?? null };
+}
+/**
+ * Compares two versions, semver-style: by the numbers, then a pre-release before its release.
+ * @param left - One.
+ * @param right - The other.
+ * @returns Negative if left is older, 0 if equal, positive if newer.
+ */
+function compare(left, right) {
+    for (let index = 0; index < 3; index += 1) {
+        const diff = left.parts[index] - right.parts[index];
+        if (diff !== 0)
+            return diff;
+    }
+    if (left.pre === right.pre)
+        return 0;
+    if (left.pre === null)
+        return 1;
+    if (right.pre === null)
+        return -1;
+    return left.pre.localeCompare(right.pre, "en", { numeric: true });
+}
+/**
+ * Whether a version is newer than another; false if either is not a version. A leading
+ * range sign is dropped, so `^0.3.0` reads as 0.3.0.
+ * @param version - The version, maybe with a range sign.
+ * @param than - The other.
+ * @returns True if it is newer.
+ * @example isNewer("1.10.0", "1.9.0") // true
+ */
+export function isNewer(version, than) {
+    const [left, right] = [parse(version.replace(/^[\^~=]/, "")), parse(than.replace(/^[\^~=]/, ""))];
+    return left !== null && right !== null && compare(left, right) > 0;
+}
+/**
+ * The first version a simple range leaves out, or null if it has no ceiling (`>=`).
+ * @param sign - `^`, `~` or `>=`.
+ * @param floor - Its version.
+ * @returns The ceiling.
+ */
+function ceiling(sign, floor) {
+    const [major, minor, patch] = floor.parts;
+    if (sign === ">=")
+        return null;
+    if (sign === "~")
+        return { parts: [major, minor + 1, 0], pre: null };
+    if (major > 0)
+        return { parts: [major + 1, 0, 0], pre: null };
+    return minor > 0 ? { parts: [0, minor + 1, 0], pre: null } : { parts: [0, 0, patch + 1], pre: null };
+}
+/**
+ * Whether the repo's version of a package reaches the one the flow was tested with, so
+ * `upgrade` keeps it: an exact version as new or newer, a range that allows it or newer
+ * (`^1.2.0` for 1.3.0, not `^0.1.0` for 0.3.0), or a source it cannot read (`workspace:*`,
+ * `github:…`, `latest`), which the repo chose on purpose.
+ * @param current - The repo's version or range.
+ * @param tested - The version the flow was tested with.
+ * @returns True to keep it.
+ * @example reaches("1.3.0", "1.2.0") // true
+ */
+export function reaches(current, tested) {
+    const wanted = parse(tested);
+    if (wanted === null)
+        return true;
+    const exact = parse(current);
+    if (exact !== null)
+        return compare(exact, wanted) >= 0;
+    const range = SIMPLE_RANGE.exec(current.trim());
+    const floor = range === null ? null : parse(range[2]);
+    if (range === null || floor === null)
+        return true;
+    if (range[1] === "=")
+        return compare(floor, wanted) >= 0;
+    const top = ceiling(range[1], floor);
+    return top === null || compare(wanted, top) < 0;
+}
+/** How a change that keeps what the repo had starts. */
+export const KEPT = "kept ";
 /** The scripts `init` adds. */
 const FLOW_SCRIPTS = {
     "issue:start": "issue-flow issue start",
@@ -5,16 +105,17 @@ const FLOW_SCRIPTS = {
     "pr:worktree": "issue-flow pr worktree",
 };
 /**
- * The dependencies the flow pins, with their versions.
+ * The dependencies the flow pins, with their versions. `issue-flow` always follows the
+ * version that runs; the other two are a floor, so `upgrade` keeps what reaches it.
  * @param versions - This package's versions.
- * @returns Package to version.
- * @example pinnedPackages(versions)["@ramon-sg/issue-flow"] // "0.1.0"
+ * @returns Package to pin.
+ * @example pinnedPackages(versions)["@ramon-sg/issue-flow"].version // "0.1.0"
  */
 export function pinnedPackages(versions) {
     return {
-        "@ramon-sg/issue-flow": versions.issueFlow,
-        "@ramon-sg/github-rest": versions.githubRest,
-        "@ramon-sg/skills-manager": versions.skillsManager,
+        [PACKAGE]: { version: versions.issueFlow, keepsReaching: false },
+        "@ramon-sg/github-rest": { version: versions.githubRest, keepsReaching: true },
+        "@ramon-sg/skills-manager": { version: versions.skillsManager, keepsReaching: true },
     };
 }
 /**
@@ -55,12 +156,12 @@ export function withFlowPackages(pkg, versions, move) {
     const next = pkg === null ? { private: true } : { ...pkg };
     const scripts = { ...(next.scripts ?? {}) };
     const changes = [];
-    for (const [name, version] of Object.entries(pinnedPackages(versions))) {
+    for (const [name, { version, keepsReaching }] of Object.entries(pinnedPackages(versions))) {
         const current = dependencyOf(next, name);
         if (current?.version === version)
             continue;
-        if (current !== null && !move) {
-            changes.push(`kept ${name} ${current.version} (issue-flow ${versions.issueFlow} was tested with ${version})`);
+        if (current !== null && (!move || (keepsReaching && reaches(current.version, version)))) {
+            changes.push(`${KEPT}${name} ${current.version} (issue-flow ${versions.issueFlow} was tested with ${version})`);
             continue;
         }
         const field = current?.field ?? "devDependencies";

package/dist/usage.d.ts

@@ -2,4 +2,4 @@
  * @file The usage text of the CLI, printed with `--help` and after a usage error.
  */
 /** Usage text. */
-export declare const USAGE = "Usage:\n  issue-flow issue branch <n>... [--namer claude|title] [--json] [-R owner/repo]\n  issue-flow issue branch --missing [--limit <n>] [--namer claude|title] [--dry-run | --yes] [--json] [-R owner/repo]\n  issue-flow issue start <n> [--branch] [--dry-run | --yes] [--resume <branch> | --new] [--no-launch]\n                             [--ask-permissions | --free] [--namer claude|title] [-R owner/repo]\n  issue-flow issue start <n> --plan [--ask-permissions | --free] [--namer claude|title] [-R owner/repo]\n  issue-flow issue start <n> --cloud | --here | --teleport | --adopt [...]\n  issue-flow worktree setup [--only <step>]\n  issue-flow worktree teardown [--path <dir>]\n  issue-flow worktree ports [--next]\n  issue-flow worktree cleanup [--path <dir>]\n  issue-flow worktree prune [--only <dir>] [--yes] [-R owner/repo]\n  issue-flow pr worktree <n> [--no-setup] [-R owner/repo] [-- [<command>...]]\n  issue-flow adapter setup [--only <step>] | issue [<url>] | archive [-R owner/repo]\n  issue-flow session\n  issue-flow hook worktree-create | worktree-remove\n  issue-flow init [--yes] [--recipe <name>,...]\n  issue-flow doctor [--json]\n  issue-flow upgrade [--dry-run]\n  issue-flow labels sync [--update] [--dry-run] [--json] [-R owner/repo]\n\nThe slug comes from the issue's \"Slug de rama\" block, then from Claude, then from the title,\nand the branch from the repo's template (an older \"Rama sugerida\" block is used if it fits).\n--missing adds the slug block to every open issue without a block, after confirming.\n\nissue start makes the branch in a worktree (or, with --branch, in this checkout), the\nstart commit, the push, the draft PR and the assignment, after confirming, and opens\nClaude: in auto mode if the repo has claude-repo-guard, with your settings with\n--ask-permissions, and with no sandbox nor questions with --free. --plan prints the branch\nand the prompt as JSON and changes nothing.\n\n--cloud confirms here and opens a Claude cloud session that starts the issue there.\n--here, inside a cloud session, starts it in this checkout and opens nothing. --teleport\nbrings the cloud session noted in the PR to the worktree. --adopt starts it in the\nworktree another tool (Orca, Paseo) just made, without asking nor opening Claude.\n\nworktree runs the steps of \"worktrees\" in .agents/flow.json: setup prepares this worktree,\nteardown cleans it before it goes (steps, ports, Docker), ports prints or moves its block\nof ports, cleanup deletes the Docker of deleted worktrees, and prune deletes the worktrees\nwhose PR was merged or closed. session is the SessionStart hook of Claude Code.\n\npr worktree makes (or reuses) a worktree on a PR's own branch, to review and fix it; with\n--, it runs the command there (Claude if none). adapter is what Orca and Paseo run: setup\nwhen they make a worktree (its steps and, if it came from an issue, issue start --adopt),\nissue to start one by hand, and archive before they delete it. hook implements Claude\nCode's WorktreeCreate and WorktreeRemove for claude --worktree.\n\ninit sets the flow up in the repo: .agents/flow.json (with the recipes its files suggest),\nthe dev dependencies and scripts, and the hooks. doctor checks them at this version, and\nupgrade moves them to this version. npx agent-kitchen runs the three, along with the\nskills, claude-cloud and claude-repo-guard.\n\nlabels sync makes in GitHub the labels the flow wants (\"labels\" in .agents/flow.json: the\nissue types and P1 to P4 by default) that the repo lacks. Names ignore case and are never\nrenamed nor deleted; --update also fixes the color and description of those that differ.";
+export declare const USAGE = "Usage:\n  issue-flow issue branch <n>... [--namer claude|title] [--json] [-R owner/repo]\n  issue-flow issue branch --missing [--limit <n>] [--namer claude|title] [--dry-run | --yes] [--json] [-R owner/repo]\n  issue-flow issue start <n> [--branch] [--dry-run | --yes] [--resume <branch> | --new] [--no-launch]\n                             [--ask-permissions | --free] [--namer claude|title] [-R owner/repo]\n  issue-flow issue start <n> --plan [--ask-permissions | --free] [--namer claude|title] [-R owner/repo]\n  issue-flow issue start <n> --cloud | --here | --teleport | --adopt [...]\n  issue-flow worktree setup [--only <step>]\n  issue-flow worktree teardown [--path <dir>]\n  issue-flow worktree ports [--next]\n  issue-flow worktree cleanup [--path <dir>]\n  issue-flow worktree prune [--only <dir>] [--yes] [-R owner/repo]\n  issue-flow pr worktree <n> [--no-setup] [-R owner/repo] [-- [<command>...]]\n  issue-flow adapter setup [--only <step>] | issue [<url>] | archive [-R owner/repo]\n  issue-flow session\n  issue-flow hook worktree-create | worktree-remove\n  issue-flow init [--yes] [--recipe <name>,...]\n  issue-flow doctor [--json]\n  issue-flow upgrade [--dry-run]\n  issue-flow labels sync [--update] [--dry-run] [--json] [-R owner/repo]\n\nThe slug comes from the issue's \"Slug de rama\" block, then from Claude, then from the title,\nand the branch from the repo's template (an older \"Rama sugerida\" block is used if it fits).\n--missing adds the slug block to every open issue without a block, after confirming.\n\nissue start makes the branch in a worktree (or, with --branch, in this checkout), the\nstart commit, the push, the draft PR and the assignment, after confirming, and opens\nClaude: in auto mode if the repo has claude-repo-guard, with your settings with\n--ask-permissions, and with no sandbox nor questions with --free. --plan prints the branch\nand the prompt as JSON and changes nothing.\n\n--cloud confirms here and opens a Claude cloud session that starts the issue there.\n--here, inside a cloud session, starts it in this checkout and opens nothing. --teleport\nbrings the cloud session noted in the PR to the worktree. --adopt starts it in the\nworktree another tool (Orca, Paseo) just made, without asking nor opening Claude.\n\nworktree runs the steps of \"worktrees\" in .agents/flow.json: setup prepares this worktree,\nteardown cleans it before it goes (steps, ports, Docker), ports prints or moves its block\nof ports, cleanup deletes the Docker of deleted worktrees, and prune deletes the worktrees\nwhose PR was merged or closed. session is the SessionStart hook of Claude Code.\n\npr worktree makes (or reuses) a worktree on a PR's own branch, to review and fix it; with\n--, it runs the command there (Claude if none). adapter is what Orca and Paseo run: setup\nwhen they make a worktree (its steps and, if it came from an issue, issue start --adopt),\nissue to start one by hand, and archive before they delete it. hook implements Claude\nCode's WorktreeCreate and WorktreeRemove for claude --worktree.\n\ninit sets the flow up in the repo: .agents/flow.json (with the recipes its files suggest),\nthe dev dependencies and scripts, and the hooks. doctor checks them at this version, and\nupgrade moves them to this version. npx agent-kitchen apply runs the three, along with the\nskills, claude-cloud and claude-repo-guard.\n\nlabels sync makes in GitHub the labels the flow wants (\"labels\" in .agents/flow.json: the\nissue types and P1 to P4 by default) that the repo lacks. Names ignore case and are never\nrenamed nor deleted; --update also fixes the color and description of those that differ.";

package/dist/usage.js

@@ -51,7 +51,7 @@ Code's WorktreeCreate and WorktreeRemove for claude --worktree.
 
 init sets the flow up in the repo: .agents/flow.json (with the recipes its files suggest),
 the dev dependencies and scripts, and the hooks. doctor checks them at this version, and
-upgrade moves them to this version. npx agent-kitchen runs the three, along with the
+upgrade moves them to this version. npx agent-kitchen apply runs the three, along with the
 skills, claude-cloud and claude-repo-guard.
 
 labels sync makes in GitHub the labels the flow wants ("labels" in .agents/flow.json: the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ramon-sg/issue-flow",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "description": "Issue-to-PR workflow for any repo: names each issue's branch, creates its worktree, opens the draft PR and launches Claude Code, locally and in Claude's cloud.",
   "license": "MIT",
   "type": "module",