@brainervirus/workit-codex 1.0.6 → 1.0.8
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@brainervirus/workit-codex",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.8",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "Workit Codex CLI/desktop plugin — shared MCP transport, hooks, and fourteen method skills",
|
|
6
6
|
"keywords": [
|
|
@@ -38,8 +38,8 @@
|
|
|
38
38
|
"build": "bun scripts/build.ts"
|
|
39
39
|
},
|
|
40
40
|
"dependencies": {
|
|
41
|
-
"@brainervirus/workit-core": "^1.0.
|
|
42
|
-
"@brainervirus/workit-mcp": "^1.0.
|
|
41
|
+
"@brainervirus/workit-core": "^1.0.8",
|
|
42
|
+
"@brainervirus/workit-mcp": "^1.0.8"
|
|
43
43
|
},
|
|
44
44
|
"engines": {
|
|
45
45
|
"node": ">=24"
|
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: workit-babysit
|
|
3
|
-
description: Use when a PR needs driving to merge-ready, CI is red, or the user says babysit
|
|
3
|
+
description: Use after creating a PR (auto-starts, drive default), when a PR needs driving to merge-ready, CI is red, or the user says babysit
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Babysit a PR to merge-ready
|
|
7
7
|
|
|
8
|
-
Babysit starts automatically on PR creation unless declined (
|
|
8
|
+
Babysit starts automatically on PR creation unless declined (`babysit:false`).
|
|
9
9
|
One babysitter per PR; never mutate PR topology (no rebase strategy changes,
|
|
10
10
|
no force-push).
|
|
11
11
|
|
|
@@ -17,8 +17,11 @@ selects requirements; do not wait for a rule that can only exist after assess.
|
|
|
17
17
|
|
|
18
18
|
## Method
|
|
19
19
|
|
|
20
|
-
1. Declare mode: drive (fix + merge
|
|
20
|
+
1. Declare mode in the same turn as the PR URL: drive (fix + merge, the
|
|
21
|
+
default), watch (report only), or threads-only.
|
|
21
22
|
2. Work the merge frontier in order: conflicts → review threads → CI.
|
|
23
|
+
Record a frontier brief (frontier state, next action) in task progress
|
|
24
|
+
per pass so the steps stay visible.
|
|
22
25
|
3. Classify CI before retry: flake (rerun once) vs stale base (verify with
|
|
23
26
|
`git merge-base --is-ancestor` before updating) vs real failure (fix).
|
|
24
27
|
4. Triage bot findings skeptically: reproduce or quote code before acting;
|