Original Summary

The test passes after the fix. But did it fail before the fix? That's one of the checks I'm building into Redpen, an open-source local CLI for the handoff after an agent says done. You define the task contract before coding. Redpen saves a Git baseline, imports completion claims from Codex, then independently runs applicable checks and produces an evidence receipt. Other agents can supply claims manually. It separates PROVEN, FAILED and UNVERIFIED instead of treating the final message as proof. For a supported focused regression, it runs the same test on the baseline and current code. A test already passing on the old code fails as regression evidence. Try it: npm install -g redpen-cli Workflow: redpen start "Fix pagination" → work with Codex → redpen import codex → redpen check The before/after verifier is still narrow: one named, unskipped dependency-free JavaScript node:test case. It doesn't prove security, compatibility or general correctness, and isn't a sandbox for untrusted project commands. I'm looking for developers willing to try one real bug fix and tell me whether the receipt makes review easier or just adds a step. Happy to help with setup. https://github.com/ChiragArora31/Redpen   submitted by   /u/Chiragarora31 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/12 20:40:23