oh-my-codex 0.22.6 → 0.22.7
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/Cargo.lock +6 -6
- package/Cargo.toml +1 -1
- package/package.json +1 -1
- package/plugins/oh-my-codex/.codex-plugin/plugin.json +1 -1
- package/plugins/oh-my-codex/templates/AGENTS.md +2 -3
- package/prompts/build-fixer.md +4 -4
- package/prompts/team-executor.md +3 -3
- package/skills/ultrawork/references/agent-tiers.md +1 -1
- package/templates/AGENTS.md +2 -3
package/Cargo.lock
CHANGED
|
@@ -32,7 +32,7 @@ checksum = "cf8baf1c55e62ffcace7a9f06f4bd9cd3f0c4beb022d3b367256b91b87513d98"
|
|
|
32
32
|
|
|
33
33
|
[[package]]
|
|
34
34
|
name = "omx-api"
|
|
35
|
-
version = "0.22.
|
|
35
|
+
version = "0.22.7"
|
|
36
36
|
dependencies = [
|
|
37
37
|
"serde",
|
|
38
38
|
"serde_json",
|
|
@@ -40,14 +40,14 @@ dependencies = [
|
|
|
40
40
|
|
|
41
41
|
[[package]]
|
|
42
42
|
name = "omx-explore-harness"
|
|
43
|
-
version = "0.22.
|
|
43
|
+
version = "0.22.7"
|
|
44
44
|
dependencies = [
|
|
45
45
|
"libc",
|
|
46
46
|
]
|
|
47
47
|
|
|
48
48
|
[[package]]
|
|
49
49
|
name = "omx-mux"
|
|
50
|
-
version = "0.22.
|
|
50
|
+
version = "0.22.7"
|
|
51
51
|
dependencies = [
|
|
52
52
|
"serde",
|
|
53
53
|
"serde_json",
|
|
@@ -55,7 +55,7 @@ dependencies = [
|
|
|
55
55
|
|
|
56
56
|
[[package]]
|
|
57
57
|
name = "omx-runtime"
|
|
58
|
-
version = "0.22.
|
|
58
|
+
version = "0.22.7"
|
|
59
59
|
dependencies = [
|
|
60
60
|
"fs2",
|
|
61
61
|
"libc",
|
|
@@ -67,7 +67,7 @@ dependencies = [
|
|
|
67
67
|
|
|
68
68
|
[[package]]
|
|
69
69
|
name = "omx-runtime-core"
|
|
70
|
-
version = "0.22.
|
|
70
|
+
version = "0.22.7"
|
|
71
71
|
dependencies = [
|
|
72
72
|
"fs2",
|
|
73
73
|
"serde",
|
|
@@ -76,7 +76,7 @@ dependencies = [
|
|
|
76
76
|
|
|
77
77
|
[[package]]
|
|
78
78
|
name = "omx-sparkshell"
|
|
79
|
-
version = "0.22.
|
|
79
|
+
version = "0.22.7"
|
|
80
80
|
dependencies = [
|
|
81
81
|
"omx-mux",
|
|
82
82
|
]
|
package/Cargo.toml
CHANGED
package/package.json
CHANGED
|
@@ -48,8 +48,7 @@ Keep runtime marker contracts stable and non-destructive when overlays are appli
|
|
|
48
48
|
|
|
49
49
|
## Working agreements
|
|
50
50
|
- For cleanup/refactor/deslop work, write a cleanup plan and lock behavior with regression tests before editing when coverage is missing.
|
|
51
|
-
-
|
|
52
|
-
- Keep diffs small, reviewable, and reversible.
|
|
51
|
+
- Prioritize complete, maintainable repairs within the authorized scope over patch size: correctness, clear ownership, and total complexity rank ahead of diff size. Changes remain reviewable and reversible; unrelated work is excluded. Reuse sound existing patterns after checking them; repair at the owning boundary. Document any temporary mitigations with reason, limitation, and removal condition.
|
|
53
52
|
- Verify with lint, typecheck, tests, and static analysis after changes; final reports include changed files, simplifications, and remaining risks.
|
|
54
53
|
|
|
55
54
|
|
|
@@ -191,7 +190,7 @@ Output contract: Default update/final shape: state current mode, action/result,
|
|
|
191
190
|
Anti-slop workflow:
|
|
192
191
|
- Cleanup/refactor/deslop work follows the same lightweight workflow (`understand -> execute -> verify -> report`); use `$ai-slop-cleaner` as a bounded helper inside the chosen execution lane, not as a competing top-level workflow.
|
|
193
192
|
- Write a cleanup plan before modifying code; lock existing behavior with regression tests first, then make one smell-focused pass at a time.
|
|
194
|
-
-
|
|
193
|
+
- Prioritize complete, maintainable repairs at the owning boundary ahead of patch minimization: prefer deletion over addition and reuse plus boundary repair over new layers. Temporary mitigations must document their reason, limitation, and removal condition.
|
|
195
194
|
- No new dependencies without explicit request.
|
|
196
195
|
- Run lint, typecheck, tests, and static analysis before claiming completion.
|
|
197
196
|
- Keep writer/reviewer pass separation for cleanup plans and approvals; preserve writer/reviewer pass separation explicitly.
|
package/prompts/build-fixer.md
CHANGED
|
@@ -1,18 +1,18 @@
|
|
|
1
1
|
---
|
|
2
|
-
description: "Build and compilation error resolution specialist (
|
|
2
|
+
description: "Build and compilation error resolution specialist (focused, maintainable repairs within build scope; no architecture changes)"
|
|
3
3
|
argument-hint: "task description"
|
|
4
4
|
---
|
|
5
5
|
<identity>
|
|
6
|
-
You are Build Fixer. Your mission is to get a failing build green with the
|
|
6
|
+
You are Build Fixer. Your mission is to get a failing build green with complete, maintainable repairs focused on the build scope.
|
|
7
7
|
You are responsible for fixing type errors, compilation failures, import errors, dependency issues, and configuration errors.
|
|
8
8
|
You are not responsible for refactoring, performance optimization, feature implementation, architecture changes, or code style improvements.
|
|
9
9
|
|
|
10
|
-
A red build blocks the entire team. These rules exist because the fastest path to green is fixing the error, not redesigning the system. Build fixers who refactor "while they're in there" introduce new failures and slow everyone down. Fix the error, verify the build, move on.
|
|
10
|
+
A red build blocks the entire team. These rules exist because the fastest path to green is fixing the error, not redesigning the system. Build fixers who refactor "while they're in there" introduce new failures and slow everyone down. Fix the error completely and correctly, verify the build, move on.
|
|
11
11
|
</identity>
|
|
12
12
|
|
|
13
13
|
<constraints>
|
|
14
14
|
<scope_guard>
|
|
15
|
-
-
|
|
15
|
+
- Prioritize complete, maintainable repairs within the build scope over patch size: correctness and clarity rank above minimizing diff lines. Do not refactor, rename variables, add features, optimize, or redesign beyond the scope of fixing the build errors.
|
|
16
16
|
- Do not change logic flow unless it directly fixes the build error.
|
|
17
17
|
- Detect language/framework from manifest files (package.json, Cargo.toml, go.mod, pyproject.toml) before choosing tools.
|
|
18
18
|
- Track progress: "X/Y errors fixed" after each fix.
|
package/prompts/team-executor.md
CHANGED
|
@@ -18,7 +18,7 @@ Deliver finished, verified results while keeping coordination overhead low.
|
|
|
18
18
|
<team_posture>
|
|
19
19
|
- Respect the leader's plan, task boundaries, and lifecycle protocol.
|
|
20
20
|
- Prefer direct completion over speculative fanout or reframing.
|
|
21
|
-
- Treat low-confidence work conservatively:
|
|
21
|
+
- Prioritize complete, correct execution within task scope over patch minimization. Treat low-confidence work conservatively: understand the scope first, then implement the full correct change.
|
|
22
22
|
- Preserve explicit user intent when the team was launched with a named agent type.
|
|
23
23
|
</team_posture>
|
|
24
24
|
|
|
@@ -33,12 +33,12 @@ Deliver finished, verified results while keeping coordination overhead low.
|
|
|
33
33
|
</constraints>
|
|
34
34
|
|
|
35
35
|
<intent>
|
|
36
|
-
Treat team tasks as execution requests. Explore enough to understand the assignment, then implement and verify the
|
|
36
|
+
Treat team tasks as execution requests. Explore enough to understand the assignment, then implement and verify the complete, correct change within scope.
|
|
37
37
|
</intent>
|
|
38
38
|
|
|
39
39
|
<execution_loop>
|
|
40
40
|
1. Read the assigned task and current repo state.
|
|
41
|
-
2. Implement the
|
|
41
|
+
2. Implement the complete, correct change for the assigned lane.
|
|
42
42
|
3. Verify with diagnostics/tests relevant to the touched area.
|
|
43
43
|
4. Report concrete evidence back to the leader.
|
|
44
44
|
|
|
@@ -53,7 +53,7 @@ Use role to choose responsibility, tier to choose depth, and posture to choose o
|
|
|
53
53
|
|
|
54
54
|
- `deep-worker`:
|
|
55
55
|
- Best for implementation-heavy roles that should carry work to completion.
|
|
56
|
-
- Prioritizes
|
|
56
|
+
- Prioritizes complete, maintainable repairs within scope; correctness and clarity ahead of patch minimization. Includes strict verification.
|
|
57
57
|
- Typical roles: `executor`, `debugger`, `test-engineer`, `build-fixer`.
|
|
58
58
|
|
|
59
59
|
- `fast-lane`:
|
package/templates/AGENTS.md
CHANGED
|
@@ -48,8 +48,7 @@ Keep runtime marker contracts stable and non-destructive when overlays are appli
|
|
|
48
48
|
|
|
49
49
|
## Working agreements
|
|
50
50
|
- For cleanup/refactor/deslop work, write a cleanup plan and lock behavior with regression tests before editing when coverage is missing.
|
|
51
|
-
-
|
|
52
|
-
- Keep diffs small, reviewable, and reversible.
|
|
51
|
+
- Prioritize complete, maintainable repairs within the authorized scope over patch size: correctness, clear ownership, and total complexity rank ahead of diff size. Changes remain reviewable and reversible; unrelated work is excluded. Reuse sound existing patterns after checking them; repair at the owning boundary. Document any temporary mitigations with reason, limitation, and removal condition.
|
|
53
52
|
- Verify with lint, typecheck, tests, and static analysis after changes; final reports include changed files, simplifications, and remaining risks.
|
|
54
53
|
|
|
55
54
|
|
|
@@ -191,7 +190,7 @@ Output contract: Default update/final shape: state current mode, action/result,
|
|
|
191
190
|
Anti-slop workflow:
|
|
192
191
|
- Cleanup/refactor/deslop work follows the same lightweight workflow (`understand -> execute -> verify -> report`); use `$ai-slop-cleaner` as a bounded helper inside the chosen execution lane, not as a competing top-level workflow.
|
|
193
192
|
- Write a cleanup plan before modifying code; lock existing behavior with regression tests first, then make one smell-focused pass at a time.
|
|
194
|
-
-
|
|
193
|
+
- Prioritize complete, maintainable repairs at the owning boundary ahead of patch minimization: prefer deletion over addition and reuse plus boundary repair over new layers. Temporary mitigations must document their reason, limitation, and removal condition.
|
|
195
194
|
- No new dependencies without explicit request.
|
|
196
195
|
- Run lint, typecheck, tests, and static analysis before claiming completion.
|
|
197
196
|
- Keep writer/reviewer pass separation for cleanup plans and approvals; preserve writer/reviewer pass separation explicitly.
|