@brainervirus/workit-codex 8.23.0 → 8.25.0
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/.codex-plugin/plugin.json +1 -1
- package/agents/workit-implementer.toml +5 -4
- package/agents/workit-verifier.toml +2 -2
- package/dist/launch-mcp.js +1136 -154
- package/dist/{workit-hook-hegafjtc.js → workit-hook-7a6v1719.js} +1368 -250
- package/dist/workit-hook.js +2 -2
- package/package.json +3 -3
- package/skills/workit-fanout/SKILL.md +1 -1
- package/skills/workit-fanout/references/brief.md +4 -4
- package/skills/workit-implement/SKILL.md +5 -5
- package/skills/workit-review/SKILL.md +5 -0
- package/skills/workit-ship/SKILL.md +1 -2
- /package/dist/{workit-hook-thet0x8m.js → workit-hook-vhz9yrcw.js} +0 -0
|
@@ -13,12 +13,13 @@ hand back), standing orders, mode (`new` or `resume`) and the worktree path.
|
|
|
13
13
|
If a field is missing, report which and stop.
|
|
14
14
|
|
|
15
15
|
1. Run each git and check command against the worktree, one verb per call:
|
|
16
|
-
`workit --cwd <worktree>
|
|
16
|
+
`workit git --cwd <worktree> commit …`, `workit check --cwd <worktree> <name>`
|
|
17
|
+
(verb first, so the host's allow rules match).
|
|
17
18
|
Never `cd <worktree> && …` chains, `$VAR` paths or compound commands. Edit
|
|
18
19
|
files by their path under the worktree. Workit's hooks deny an edit or a
|
|
19
20
|
mutating git command outside it.
|
|
20
21
|
2. The worktree is already on the brief's branch. If it is not: `MODE: new`,
|
|
21
|
-
`workit --cwd <worktree>
|
|
22
|
+
`workit git --cwd <worktree> branch <branch> --base <base>`; `MODE: resume`
|
|
22
23
|
(you replace a stopped worker), `git -C <worktree> switch <branch>` and
|
|
23
24
|
continue from its head. A hook denies protected or non-compliant names;
|
|
24
25
|
follow the unblock it prints.
|
|
@@ -29,8 +30,8 @@ If a field is missing, report which and stop.
|
|
|
29
30
|
Stop only for an irreversible or security-sensitive action, or a side effect
|
|
30
31
|
outside your worktree.
|
|
31
32
|
5. Commit in small steps with
|
|
32
|
-
`workit --cwd <worktree>
|
|
33
|
-
6. Run every verify command as `workit --cwd <worktree>
|
|
33
|
+
`workit git --cwd <worktree> commit -m "<conventional message>" -- <paths in scope>`.
|
|
34
|
+
6. Run every verify command as `workit check --cwd <worktree> …` and keep the
|
|
34
35
|
real exit codes.
|
|
35
36
|
7. Never record a verdict on your own work and never pass `--self`: a separate
|
|
36
37
|
verifier judges it. Never push, open a PR, rebase or merge unless the brief
|
|
@@ -8,8 +8,8 @@ backward: what must be true, what must exist, what must be wired. The author's
|
|
|
8
8
|
summary is a claim, not evidence; assume the goal is not met until you observe
|
|
9
9
|
it.
|
|
10
10
|
|
|
11
|
-
1. Pin the candidate in its own checkout (run workit
|
|
12
|
-
never `cd` first): `git -C <worktree> rev-parse HEAD` and `git -C <worktree> status --short`. A dirty tree
|
|
11
|
+
1. Pin the candidate in its own checkout (run workit as
|
|
12
|
+
`workit <verb> --cwd <worktree> …`, verb first; never `cd` first): `git -C <worktree> rev-parse HEAD` and `git -C <worktree> status --short`. A dirty tree
|
|
13
13
|
or a moving HEAD is itself a finding, and the ledger refuses a verdict on it.
|
|
14
14
|
2. Read the brief: goal, acceptance (Given/When/Then), verify commands.
|
|
15
15
|
3. Run every verify command through the CLI so the result is observed:
|