@voidlabs.gg/voidshift 0.4.4 → 0.4.5

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.
Files changed (2) hide show
  1. package/README.md +39 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -86,8 +86,33 @@ vsf agents workflow add|edit|show|rename|move|rm
86
86
  vsf agents projects | project add|edit|show|rename|rm
87
87
  vsf agents homes | link DIR # where the agents are installed
88
88
  vsf agents clean # old worktrees and run logs
89
+ vsf agents validate [DIR] # check the config and agent folders
89
90
  ```
90
91
 
92
+ A workflow can also be a folder you write by hand,
93
+ `~/.config/voidshift/agents/defs/NAME/agent.json`, with its prompt files next to
94
+ it. Steps are the built-in ids above or your own:
95
+
96
+ ```json
97
+ {
98
+ "triggers": [{ "source": "cron", "schedule": "0 7 * * 1-5", "task": "Morning brief" }],
99
+ "steps": [{ "id": "brief", "prompt": "brief.md", "output": "none", "model": "haiku", "timeoutMinutes": 10 }],
100
+ "maxRounds": 1,
101
+ "project": "tether-relay",
102
+ "writeBack": { "labels": true, "state": null, "comment": true }
103
+ }
104
+ ```
105
+
106
+ A step's `output` is `plan`, `verdict`, `commits`, `publish` or `none`; a failed
107
+ `verdict` sends the work back to the nearest `plan` or `commits` step. `engine`,
108
+ `model` and `timeoutMinutes` fall back to the config, and `write` to true only
109
+ for `commits`. A `publish` step takes no prompt; the others take one `prompt`
110
+ file or `skill`, which must ask for a `RESULT:` line (`plan`, `commits`) or a
111
+ `VERDICT:` line (`verdict`). `writeBack` applies to card runs: `state` moves a
112
+ verified card there (`null` never moves it), `labels: false` only takes the
113
+ trigger label off, and `comment: false` skips the closing comment. Edit the file,
114
+ then `vsf agents validate`.
115
+
91
116
  ### memory
92
117
 
93
118
  A folder of markdown notes, one topic per note, with an `INDEX.md` holding one
@@ -108,6 +133,20 @@ vsf memory on | off # turn recall on or off
108
133
  Setup creates a vault at `~/memory` or uses one you already have. Codex asks you
109
134
  to trust the recall hook once: run `/hooks` in Codex.
110
135
 
136
+ ### Your profile
137
+
138
+ Every agent run carries your profile, on any machine, without touching your
139
+ Claude or Codex folder. `vsf agents profile init` creates
140
+ `~/.config/voidshift/agents/profile/`:
141
+
142
+ - `RULES.md` is added to every step's prompt (style, commit rules, tone).
143
+ - `claude-settings.json` is passed to Claude runs with `--settings`, so hooks
144
+ come along. `{{profile}}` stands for the folder, so hook scripts can live in it.
145
+
146
+ Setup also asks what the runner does to agent commits before it pushes them:
147
+ remove AI co-author lines, and add `Signed-off-by` for repos that ask for a
148
+ DCO. Only the new commits of that step are rewritten, never pushed ones.
149
+
111
150
  ## What to know
112
151
 
113
152
  - **Your own logins.** Agents run the official `claude` and `codex` CLIs you
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@voidlabs.gg/voidshift",
3
- "version": "0.4.4",
3
+ "version": "0.4.5",
4
4
  "description": "One CLI for the Void dev tools: keep your Mac awake, run agents in the background, shared skills and memory for Claude Code and Codex.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {