@a5c-ai/babysitter-github 5.0.1-staging.16f8c86f4 → 5.0.1-staging.19eb57a3c2fd

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/README.md CHANGED
@@ -18,7 +18,8 @@ directly.
18
18
  - **Node.js 22+**
19
19
  - **GitHub Copilot CLI** (`copilot`) -- requires an active GitHub Copilot
20
20
  subscription
21
- - **Babysitter SDK CLI** (`@a5c-ai/babysitter-sdk`) -- installed globally
21
+ - **Babysitter CLI** (`@a5c-ai/babysitter`) -- installed globally when using
22
+ the SDK helper
22
23
 
23
24
  ## Installation
24
25
 
@@ -42,22 +43,31 @@ Install directly from the generated external plugin repository:
42
43
  copilot plugin install a5c-ai/babysitter-github-copilot
43
44
  ```
44
45
 
45
- ### Alternative Installation (npm / development)
46
+ ### Alternative Installation (SDK helper / development)
46
47
 
47
- For development or environments where the Copilot CLI plugin system is not
48
- available, install via npm:
48
+ For development, automation, or environments where the Copilot CLI plugin system is not available, install through the Babysitter SDK helper. This is the canonical scriptable path used by the installer tests and resolves to `npx --yes @a5c-ai/babysitter-github install ...` under the hood:
49
49
 
50
- Install the SDK CLI first:
50
+ Install the Babysitter CLI first:
51
51
 
52
52
  ```bash
53
- npm install -g @a5c-ai/babysitter-sdk
53
+ npm install -g @a5c-ai/babysitter
54
54
  ```
55
55
 
56
- Then install the GitHub Copilot plugin globally:
56
+ Then install the GitHub Copilot plugin globally or into a workspace:
57
57
 
58
58
  ```bash
59
- npm install -g @a5c-ai/babysitter-github
60
- babysitter-github install
59
+ # Global install
60
+ babysitter harness:install-plugin github-copilot
61
+
62
+ # Workspace install
63
+ babysitter harness:install-plugin github-copilot --workspace /path/to/repo
64
+ ```
65
+
66
+ You can also run the published package installer directly:
67
+
68
+ ```bash
69
+ npx --yes @a5c-ai/babysitter-github install --global
70
+ npx --yes @a5c-ai/babysitter-github install --workspace /path/to/repo
61
71
  ```
62
72
 
63
73
  Or install from generated source:
@@ -67,10 +77,10 @@ npm run generate:plugins
67
77
  node artifacts/generated-plugins/github-copilot/bin/install.js
68
78
  ```
69
79
 
70
- Install into a specific workspace:
80
+ Install into a specific workspace from generated source:
71
81
 
72
82
  ```bash
73
- babysitter-github install --workspace /path/to/repo
83
+ node artifacts/generated-plugins/github-copilot/bin/install.js --workspace /path/to/repo
74
84
  ```
75
85
 
76
86
  ### GitHub Copilot cloud agent installation
@@ -104,7 +104,7 @@ function ensureMarketplaceEntry(marketplacePath, pluginRoot) {
104
104
  name: PLUGIN_NAME,
105
105
  source: relSource,
106
106
  description: "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
107
- version: "5.0.1-staging.16f8c86f4",
107
+ version: "5.0.1-staging.19eb57a3c2fd",
108
108
  author: { name: "a5c.ai" },
109
109
  };
110
110
  if (idx >= 0) marketplace.plugins[idx] = entry;
package/commands/call.md CHANGED
@@ -4,4 +4,8 @@ argument-hint: Specific instructions for the run.
4
4
  allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
5
5
  ---
6
6
 
7
- Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
7
+ Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). Then continue executing the returned instructions in this same turn. Do not stop after the Skill tool returns; carry the requested run through to completion proof.
8
+
9
+ User arguments for this command:
10
+
11
+ $ARGUMENTS
package/commands/yolo.md CHANGED
@@ -1,7 +1,11 @@
1
- ---
2
- description: Orchestrate a babysitter run. use this command to start babysitting a complex workflow in a non-interactive mode, without any user interaction or breakpoints in the run.
3
- argument-hint: Specific instructions for the run.
4
- allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
5
- ---
6
-
7
- Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). but without any user interaction or breakpoints in the run.
1
+ ---
2
+ description: Orchestrate a babysitter run. use this command to start babysitting a complex workflow in a non-interactive mode, without any user interaction or breakpoints in the run.
3
+ argument-hint: Specific instructions for the run.
4
+ allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
5
+ ---
6
+
7
+ Start the Babysitter run directly through the CLI, without any user interaction or breakpoints. Do not invoke the Skill tool and do not run an instructions-only command. In Claude Code, use Bash to run `babysitter-agent yolo --harness claude-code --workspace "$PWD" --prompt "<user arguments>" --json`; in Codex, run `babysitter-agent yolo --harness codex --workspace "$PWD" --prompt "<user arguments>" --json`; in other harnesses, use the same command with that harness id. Replace `<user arguments>` with the arguments shown below, wait for the command to finish, and treat the CLI completion proof as the result.
8
+
9
+ User arguments for this command:
10
+
11
+ $ARGUMENTS
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@a5c-ai/babysitter-github",
3
- "version": "5.0.1-staging.16f8c86f4",
3
+ "version": "5.0.1-staging.19eb57a3c2fd",
4
4
  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
5
5
  "scripts": {
6
6
  "deploy": "npm publish --access public",
@@ -36,7 +36,7 @@
36
36
  "access": "public"
37
37
  },
38
38
  "dependencies": {
39
- "@a5c-ai/babysitter-sdk": "5.0.1-staging.16f8c86f4"
39
+ "@a5c-ai/babysitter-sdk": "5.0.1-staging.19eb57a3c2fd"
40
40
  },
41
41
  "repository": {
42
42
  "type": "git",
package/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "babysitter",
3
- "version": "5.0.1-staging.16f8c86f4",
3
+ "version": "5.0.1-staging.19eb57a3c2fd",
4
4
  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval",
5
5
  "author": {
6
6
  "name": "a5c.ai"
@@ -5,4 +5,8 @@ description: Orchestrate a babysitter run. use this command to start babysitting
5
5
 
6
6
  # call
7
7
 
8
- Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
8
+ Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). Then continue executing the returned instructions in this same turn. Do not stop after the Skill tool returns; carry the requested run through to completion proof.
9
+
10
+ User arguments for this command:
11
+
12
+ $ARGUMENTS
@@ -5,4 +5,8 @@ description: Orchestrate a babysitter run. use this command to start babysitting
5
5
 
6
6
  # yolo
7
7
 
8
- Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). but without any user interaction or breakpoints in the run.
8
+ Start the Babysitter run directly through the CLI, without any user interaction or breakpoints. Do not invoke the Skill tool and do not run an instructions-only command. In Claude Code, use Bash to run `babysitter-agent yolo --harness claude-code --workspace "$PWD" --prompt "<user arguments>" --json`; in Codex, run `babysitter-agent yolo --harness codex --workspace "$PWD" --prompt "<user arguments>" --json`; in other harnesses, use the same command with that harness id. Replace `<user arguments>` with the arguments shown below, wait for the command to finish, and treat the CLI completion proof as the result.
9
+
10
+ User arguments for this command:
11
+
12
+ $ARGUMENTS
package/versions.json CHANGED
@@ -1,4 +1,4 @@
1
1
  {
2
- "sdkVersion": "5.0.1-staging.16f8c86f4",
3
- "extensionVersion": "5.0.1-staging.16f8c86f4"
2
+ "sdkVersion": "5.0.1-staging.19eb57a3c2fd",
3
+ "extensionVersion": "5.0.1-staging.19eb57a3c2fd"
4
4
  }