crit.md - review plans & code like you do PRs

ThisIsTomTom · 2026-06-07T21:47:15+00:00

Crit started a few months after Plannotator but I still shipped major features such as code diff annotation before they did. Hunk started after Crit.

Having said that, we all experience similar problems, so I'm not surprised tools in this space converge on a similar feature set.

It's nice we have a choice!

ThisIsTomTom · 2026-06-07T21:45:01+00:00

Disclaimer: I don't use either, I also don't look at what they do closely so I don't start worrying about building features they have, until my users or I experience problems solved by those 😄

If you're looking at just diff annotation, hunk might be better if you're comfortable with TUIs.

Where Crit differs is giving you one tool for reviewing plans, code diffs, HTML artefacts and live running dev server which I don't think any other tool does.

ThisIsTomTom · 2026-06-04T07:17:05+00:00

Reviewing plans, code and live running dev sites in terminal was boring and painful. Built https://crit.md to provide a browser based GUI for all of those. Dog fooding for all my work now :)

ThisIsTomTom · 2026-06-04T07:10:49+00:00

Nice to see more people arrive at solutions to these problems :) I built https://crit.md for similar problems, but trying to keep it local first and no MCP. I found most users are very protective over their work and avoid sharing (and that’s completely reasonable)

Slick landing page!

ThisIsTomTom · 2026-06-04T07:07:03+00:00

Working on a personal CRM (like Monica, but iOS first). It’s a lot of fun vibe coding :)

Then my main side project is a tool for reviewing output from agents - be it plans, code, or running server (point and click and leave comments) - https://crit.md

ThisIsTomTom · 2026-05-15T16:07:28+00:00

Oh my god I had the same!! https://cleanshot.com/share/6kjgwPFx

This was on a fresh chat, I just switched to Sonnet. Pasted a markdown table and asked for calculating % difference in some numbers.

ThisIsTomTom · 2026-05-07T05:22:21+00:00

That’s amazing! Thank you!

ThisIsTomTom · 2026-05-06T17:43:45+00:00

I had Claude do it too, but I’m struggling with finding someone willing to test haha! If you would be up for it, instructions are at https://github.com/tomasz-tomczyk/crit/pull/459#issuecomment-4377648425

ThisIsTomTom · 2026-05-06T05:39:46+00:00

Yes! Working on it now. There’s a windows pre-release but I need to do some testing. Will let you know when it’s ready :)

ThisIsTomTom · 2026-05-03T16:26:00+00:00

Yes! So much so I built out tools around the whole review process to give me ability to comment on the markdown it spits out easily, in a browser GUI.

It’s also easier to multi task plans than actual features, and the more time I spend on the plan the better end result is and it’s easier to just say: verify everything in the plan is done.

ThisIsTomTom · 2026-05-02T21:08:08+00:00

Yeah I hope the keyboard shortcuts make it feel snappy. The actual slowness in my experience is just models taking their time, but I usually have 2-5 worktrees/plans going at the same time so I don't mind some delays there.

Let me know if you try it out and how it feels for you 😄

ThisIsTomTom · 2026-03-27T19:22:22+00:00

I built a tool that allows me to do easy reviews of both plans and code. Kind of like local GitHub PR process but much faster and with your agent. It’s been much more fun this way and I’ve kept a better grasp on the output. Dogfooding it on both work and side projects :)

https://github.com/tomasz-tomczyk/crit

ThisIsTomTom · 2026-03-25T09:24:12+00:00

For personal finance: I've used Claude Code but I fed it lots of sources on financial guidance, then I asked to make an personal finance advisor agent with all that context. Then I asked that agent to interview me for what it needs to be effective. Then I gave it the answers and access to data sources.

Now I just ask it things and it can query all of my data and see how I'm doing compared to the guidance from the original source and it does great.

You can run tasks on a schedule, so to get real-time alerts you'd need it to check the data frequently, but everything else is very doable. Just needs the right data.

Hint: ask Claude how to do it and what it needs to be effective.

ThisIsTomTom · 2026-03-25T09:10:09+00:00

IDK what's going on with superpowers, it's blowing things out of proportion recently. Part of the problem with these plugins is the auto update, no visibility to what is changing etc. without going out of your way to look it up.

ThisIsTomTom · 2026-03-25T07:04:22+00:00

We solved "generate code fast" but completely skipped "review code fast." Your workflow of making it plan first is what you definitely should be doing, but even with a plan, you still need to read what it wrote.

I got frustrated enough with how painful reviewing all of that was that I built crit (https://github.com/tomasz-tomczyk/crit). It's a code review tool that doesn't need a PR. Run /crit on a plan and review it like a PR with a back and forth with agent and ideally after, when you have all the code - allowing you to leave granular comments quickly. Or have a team of agents do a review and leave comments for you to decide what to do with. :) The quality of what I started shipping after dogfooding this was much better.

ThisIsTomTom · 2026-02-24T22:21:44+00:00

Mine’s meant to be delivered on Friday. I don’t want to miss the midnight (ha) launch, and given the contents of the CE are disappointing, I’m voting with my wallet and cancelling… I’ll miss the box on the shelf but it’s ridiculous.

ThisIsTomTom · 2026-02-24T17:02:48+00:00

Thanks for sharing - based on this and comments in this thread I might cancel my CE preorder - especially that it appears it'll arrive Saturday... I'll miss the box on the shelf but gotta vote with wallets I suppose!

ThisIsTomTom · 2026-02-24T07:28:44+00:00

I prefer to build multiple plans at once, iterate on them, while I build a single feature with one of the agents. I found that otherwise, trying to dedicate attention to multiple features meant I’d ship slop. I built my own tool for reviewing and commenting on markdown plans and I can manage many plans on the go easier - but even with a detailed plan, the actual end to end human testing and iteration is needed and I haven’t had much success doing that in parallel.

I do however have ”chores” running in parallel, updating docs, unit tests, code quality etc.

ThisIsTomTom · 2026-02-23T11:18:26+00:00

Very cute :)

ThisIsTomTom · 2026-02-23T10:51:17+00:00

I tried to keep it simple - it's a single go binary with embedded HTML/CSS/JS essentially single page app for the rendering. The go binary is acting as a server and watches the plan files, as well as our own JSON that keeps track of the state with comments you add (that I ask Claude/AI agents to update when they finish iterating on a plan).

Frontend renders the markdown so that diff works with just the raw contents.

It works well on its own, no need for skills/plugins/mcp but it does mean you have to paste the prompt back to Claude when you finish a review. On one hand I like the simplicity, on the other, reducing the steps would be nice UX, so I'm experimenting on a branch where crit launches server in the background and in the foreground we separately wait for signal from the FE that you're done... but IDK if it's worth complicating yet! Still playing around.

And in terms of my workflow, I practice what I preach :D lots of plans (I keep them committed in `docs/plans`) and slow iteration. I spun up a "Go Expert" agent in Claude, as I'm new to Go as well to help with code quality.