thempatel

I built my own for a specific review use case: improving code modularity and minimizing slop. Forcing the agent to use it in a loop to clean up the diff means that I get something cleaner to review manually

https://github.com/thempatel/mdlr

Thank you so much! I am open to any and all feedback. Please file an issue or discussion if you have things you'd like to share.

Getting this onto crates.io is a great suggestion, I will look into that!

I think the problem is that agents are inherently stochastic. Their idea of simplification changes from message to message because whatever objective it’s operating on internally is inherently opaque and changes. No matter how much you prompt it, eventually it’s going to not do what you want it to do.

I built https://github.com/thempatel/mdlr for precisely this reason: externalize the objective and force the agent to meet it.

I wrote a tool to give agents signal on what is and isn't clean code. I find myself spending an inordinate amount of time reviewing agent code.

After asking agents to make the same types of changes over and over again, I decided to make a tool that would just tell the agent that its code needs improving. I figured that if I could get the agent to self-review and improve the code it writes, that it would save me time when I finally come around to reviewing it.

Tool: https://github.com/thempatel/mdlr Blog: https://www.thempatel.com/2026/06/06/slop.html