@the-open-engine-company/zeroshot 11.0.0 → 11.1.0

package/README.md

@@ -1,9 +1,10 @@
 # `@the-open-engine-company/zeroshot`
 
-Zeroshot enforces your team's QA process on coding agents. You define the process as a graph:
-which agents implement, which reviewers and tests a change must pass, where failures go for repair,
-and where a run stops. Every task runs through it, and no agent can skip a step. It works with
-Codex, Claude Code, GitHub Copilot and Pi.
+zeroshot is the open-source engine for autonomous software production. Its workflow engine
+orchestrates coding agents through implementation, independent code review, testing, repair
+and delivery. Define your team's development and QA process as a reusable multi-agent graph;
+the engine enforces its transitions and retry limits. It works with Codex, Claude Code,
+GitHub Copilot and Pi.
 
 This package is the installer for the canonical `zeroshot` executable and agent skills. The package selects the release
 archive for the current Node platform and architecture, verifies it against that release's
@@ -21,7 +22,20 @@ Claude Code at `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/skills/<name>/SKILL.md`. Rei
 managed copy. A conflicting or edited skill is preserved; installation fails with the exact path so
 the conflict cannot pass unnoticed.
 
-When set, `CLAUDE_CONFIG_DIR` must be absolute so the managed skills have stable locations.
+Set `ZEROSHOT_SKIP_SKILLS=1` to install or update only the executables:
+
+```sh
+ZEROSHOT_SKIP_SKILLS=1 npm install --global @the-open-engine-company/zeroshot
+ZEROSHOT_SKIP_SKILLS=1 zeroshot update
+```
+
+Only the exact value `1` enables this opt-out. Export it in your shell configuration to keep later
+installs and updates from recreating removed skills. Existing skills are left untouched, and skill
+conflicts or unwritable destinations do not block executable installation. Unset it to restore
+automatic skill installation.
+
+With automatic skill installation enabled, `CLAUDE_CONFIG_DIR` must be absolute when set so the
+managed skills have stable locations.
 
 npm 7 and newer do not run uninstall lifecycle scripts. After uninstalling the package, remove the
 managed skill directories above manually if their `SKILL.md` files are still unmodified managed copies.

package/lib/skills.js

@@ -137,9 +137,11 @@ function installAt(location, canonical, managed) {
 }
 
 function installSkills(options = {}) {
+  const environment = options.environment ?? process.env;
+  if (environment.ZEROSHOT_SKIP_SKILLS === '1') return [];
+
   const packageRoot = options.packageRoot || path.resolve(__dirname, '..');
   const homeDirectory = options.homeDirectory ?? os.homedir();
-  const environment = options.environment ?? process.env;
   const uid = options.uid ?? (typeof process.getuid === 'function' ? process.getuid() : undefined);
   const sources = SKILL_NAMES.map((skill) => {
     const canonical = fs.readFileSync(path.join(packageRoot, 'skills', skill, 'SKILL.md'), 'utf8');

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@the-open-engine-company/zeroshot",
-  "version": "11.0.0",
-  "description": "Enforces your team's QA process on coding agents. Define the workflow as a graph of implementers, reviewers, tests and repair loops; every task runs through it and no agent can skip a step. Works with Codex, Claude Code, GitHub Copilot and Pi.",
+  "version": "11.1.0",
+  "description": "The open-source engine for autonomous software production. Orchestrate coding agents through implementation, code review, testing and repair.",
   "keywords": [
     "claude-code",
     "codex",
@@ -12,7 +12,10 @@
     "agent-orchestration",
     "code-review",
     "verification",
-    "cli"
+    "cli",
+    "autonomous-software-production",
+    "workflow-engine",
+    "qa-automation"
   ],
   "homepage": "https://zeroshot.sh",
   "license": "MIT",

package/skills/zeroshot/SKILL.md

@@ -112,9 +112,9 @@ When no saved profile fits and the user has not asked for Platform, run the buil
 
 ## Review an issue or pull request
 
-The `pr-review` and `issue-review` templates post reports as comments by default.
+The `pr-review`, `code-review` and `issue-review` templates post reports as comments by default.
 PR review classifies whether reproduction is necessary, runs required full-stack checks (including
-a browser for UI changes), then checks the diff and linked issue coverage. Its final report is concise. PR review uses comment delivery; issue review also supports `--delivery none` for a report without publication. Supply an issue or PR URL through `--task-from`, which resolves
+a browser for UI changes), then checks the diff and linked issue coverage. Its final report is concise. `code-review` takes the same PR input and runs parallel specialist reviewers whose verified findings become one comment. Both PR templates use comment delivery; issue review also supports `--delivery none` for a report without publication. Supply an issue or PR URL through `--task-from`, which resolves
 title/body and pins source before execution:
 
 ```console