@brainervirus/workit-opencode 1.0.8 → 1.0.10
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/assets/skills/workit-babysit/SKILL.md +3 -1
- package/assets/skills/workit-plan/SKILL.md +14 -2
- package/dist/plugin.js +1014 -339
- package/package.json +2 -2
|
@@ -7,7 +7,9 @@ description: Use after creating a PR (auto-starts, drive default), when a PR nee
|
|
|
7
7
|
|
|
8
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
|
-
no force-push).
|
|
10
|
+
no force-push). When a PR URL is observed from a route Workit did not enforce
|
|
11
|
+
(for example a raw `gh pr create` the host allowed), load this skill and drive
|
|
12
|
+
that PR anyway; do not claim the Workit route was enforced.
|
|
11
13
|
|
|
12
14
|
## Before method work
|
|
13
15
|
|
|
@@ -22,9 +22,21 @@ selects requirements; do not wait for a rule that can only exist after assess.
|
|
|
22
22
|
needed, owner, and next action. Keep the plan against the existing system.
|
|
23
23
|
3. If policy separately requires a durable specification, record that behavior
|
|
24
24
|
agreement; otherwise do not invent a spec. A plan without a spec is valid.
|
|
25
|
-
4.
|
|
25
|
+
4. Present before asking: show durable artifacts as a complete digest plus the
|
|
26
|
+
exact path and inline plans as their content. Never ask the user to approve
|
|
27
|
+
something they have not seen, and keep the question to one short scoped
|
|
28
|
+
sentence.
|
|
29
|
+
5. Execute an approved plan continuously: one atomic commit per task after its
|
|
30
|
+
checks pass, no "continue?" prompts. Stop only for a new product decision, a
|
|
31
|
+
failed safety or verification gate, a conflicting concurrent edit, or missing
|
|
32
|
+
authority.
|
|
33
|
+
6. Record the plan's commit list once through the plan-scoped action approval
|
|
34
|
+
(`git.commit` with `plan_steps` and `plan_branch`) so each listed commit runs
|
|
35
|
+
without a new question; an unlisted message, a branch change, or any change to
|
|
36
|
+
the plan needs a fresh exact approval.
|
|
37
|
+
7. Update the shared task progress at meaningful boundaries. Reassess when facts,
|
|
26
38
|
dependencies, or scope change; preserve unresolved blockers and decisions.
|
|
27
|
-
|
|
39
|
+
8. On steering (new instructions mid-task): apply `workit-steer` — park state
|
|
28
40
|
verbatim, classify same-task / new-task / quick-question, handle, re-anchor.
|
|
29
41
|
|
|
30
42
|
Use shared task/progress and evidence operations. Do not create a universal
|