I built crt to help reduce the burden of reviewing AI generated code.
As fun as it is to vibecode software to production, sometimes you still need to understand and be responsible for the code that agents write. "It's the agents fault" doesn't work as an excuse for many types of software.
Agents are great (and prolific) at writing code, but not so great at engineering software and I wanted a convenient way to review AI output and iterate on the parts that needed work without needing to re-review things that I was happy with, and thus crt was born.
You run it on your code base it shows you all files that have changed since a given commit, and all the diffs for those files. You approve files that you are happy with, and leave comments on sections of code that still need work.
Then you point your agent at crt over mcp, and it reads all your comments and you work with the agent to address them. This feedback loop is where crt shines because it reduces the manual effort involved in trying to tell an agent which parts of the code have a problem.
crt updates the diffs as this happens, only showing changes since the most recent approval, and you continue with the comment/mcp/agent feedback loop until you are happy with all the code.
It's still very much a work in progress but works well enough I've been using (and improving) it daily for the last few months.
Comments URL: [https://news.ycombinator.com/item?id=49761478](https://news.ycombinator.com/item?id=49761478)
Points: 1