Original Summary

i'm building Empryo, an AI coding agent. one thing i wanted was to stop fixing a pattern only for another agent to write it again later! so the bug workflow has separate jobs: reproduce it in an isolated home, have another agent confirm it, fix it with before/after proof, then review the fix. for patterns a linter can recognise, the fixer writes a GritQL rule in Biome too. it must flag a bad fixture and pass a good one before i scan the actual codebase. it won't catch every version of a bug, but it gives the next agent a check instead of another paragraph of instructions. the handoffs are markdown files. folders hold the state and an atomic mkdir claims a record. disputed reports come back to me. i put the workflow in a public skill so u can try the idea without using Empryo: https://github.com/proxysoul/SoulStack/tree/main/skills/immune-system start with one bug if u try it. getting the review right matters more than adding more agents.   submitted by   /u/slugfingers-kun [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/27 21:29:42