A test-driven coding agent workflow with Jev and Opus 5.5
Test results feed every next-step decision: Jev makes a typed choice among inspect, patch, test, ask and finish, Opus writes the patch, and failing cases loop back until a PR draft carries the verification record.
Jev + Opus 5.5: code generation with test results fed into every next-step decision. This setup takes the agent from issue inspection to a change ready for review. Here’s how: /scope → Opus 5.5 reads the issue + repo rules. Define expected behavior, acceptance checks and the smallest useful fix. /state → collect the repro, failing test, relevant files, changed paths and unresolved questions. /choice → Jev selects the next available action: inspect / patch / test / ask / finish. Return a typed choice; use configured uncertainty handling. /patch → Opus writes a focused change + regression test. Explain which behavior should change and why. /checks → build the modified version, run the targeted test, then related checks. Capture exit codes + failure logs. In the demo, an edge case still fails. /recheck → feed new logs back into state. Jev chooses the next step; Opus repairs the remaining issue and tools rerun the checks. Enforce limits in code. /review → return the diff, test evidence and remaining risks in a PR draft. Auto-merge stays OFF. The result: a failed test becomes input for the next decision, and the final PR draft carries the verification record. Save this for your next coding agent setup ↓
This post quotes another post: x.com/0xchonsy/status/2107125199028044001