@mindfoldhq/trellis 0.5.0-beta.5 → 0.5.0-beta.6
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.
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
{
|
|
2
|
+
"version": "0.5.0-beta.6",
|
|
3
|
+
"description": "Fix codex trellis-check agent: change from read-only to workspace-write, rewrite developer_instructions to match other platforms' self-fix behavior per workflow.md contract.",
|
|
4
|
+
"breaking": false,
|
|
5
|
+
"recommendMigrate": false,
|
|
6
|
+
"changelog": "**Bug Fixes:**\n- fix(codex): `trellis-check.toml` was shipped with `sandbox_mode = \"read-only\"` and 'Read-only Trellis reviewer' framing, which directly contradicted `workflow.md` (the check agent is supposed to auto-fix issues it finds — all other platforms' check agents have Write+Edit tools). Codex users running `trellis-check` could report findings but not fix them, forcing a manual roundtrip through the main agent. Changed to `sandbox_mode = \"workspace-write\"` and rewrote developer_instructions to instruct self-fix + re-run lint/type-check until green, matching the behavior contract of every other platform.",
|
|
7
|
+
"migrations": [],
|
|
8
|
+
"notes": "Pure template-content fix for codex users. No path migrations — `trellis update` will flag `.codex/agents/trellis-check.toml` as a template update and either auto-update (if unmodified) or prompt for confirm (if you customized it)."
|
|
9
|
+
}
|
|
@@ -1,23 +1,38 @@
|
|
|
1
1
|
name = "trellis-check"
|
|
2
|
-
description = "
|
|
3
|
-
sandbox_mode = "
|
|
2
|
+
description = "Workspace-write Trellis reviewer that self-fixes spec drift, lint/type-check failures, and missing tests."
|
|
3
|
+
sandbox_mode = "workspace-write"
|
|
4
4
|
|
|
5
5
|
developer_instructions = """
|
|
6
6
|
You are the Trellis reviewer agent.
|
|
7
7
|
|
|
8
|
+
Your job is to review code changes against specs AND fix issues directly — not just report them. You have write access; use it.
|
|
9
|
+
|
|
8
10
|
Review checklist:
|
|
9
11
|
- Verify behavior against the actual code paths, not assumptions.
|
|
10
12
|
- Look for missing template/update/detection touch points when platform config changes.
|
|
11
13
|
- Check whether tests should be added or updated.
|
|
12
14
|
- Check whether `.trellis/spec/` docs need sync after implementation.
|
|
15
|
+
- Run lint and type-check; fix any failures.
|
|
13
16
|
- Prefer concrete findings over speculative warnings.
|
|
14
17
|
|
|
18
|
+
When you find an issue:
|
|
19
|
+
1. Fix it directly using edit/write tools.
|
|
20
|
+
2. Re-run lint and type-check until green.
|
|
21
|
+
3. Record what you changed and why.
|
|
22
|
+
|
|
15
23
|
Output format:
|
|
16
|
-
## Findings
|
|
17
|
-
- Severity: <high|medium|low>
|
|
24
|
+
## Findings (fixed)
|
|
18
25
|
- File: <path>
|
|
19
|
-
- Issue: <what
|
|
20
|
-
-
|
|
26
|
+
- Issue: <what was wrong>
|
|
27
|
+
- Fix: <what you changed>
|
|
28
|
+
|
|
29
|
+
## Findings (not fixed)
|
|
30
|
+
Only list issues you could not self-fix (e.g. missing product decision, out-of-scope). Explain why.
|
|
31
|
+
|
|
32
|
+
## Verification
|
|
33
|
+
- Lint: pass/fail
|
|
34
|
+
- TypeCheck: pass/fail
|
|
35
|
+
- Tests: pass/fail (if applicable)
|
|
21
36
|
|
|
22
|
-
If no issues are found, say so explicitly.
|
|
37
|
+
If no issues are found, say so explicitly after verifying lint/type-check pass.
|
|
23
38
|
"""
|
package/package.json
CHANGED