I think tools like this are needed and will become standard in the near future.

However, the backend demo report seems longer and more complex than just reading the code. I’m trying to build something similar as well, and no one has quite nailed this yet.

The risk map / assisted review needs to be succinct and information dense, to guide your attention. My current philosophy is that we need to be annotating code, not replacing the entire code review interface with a bunch of text.

Looked at the backend demo, and the first lines suggested to look at were importing things. Exactly what I really don't need to be reviewing

why is the only comment by the OP flagged and dead? Is it because they were supposed to include that data in the description text rather than a comment, was it flagged as AI generated, or..?

Trying to understand why the poster's own comment was flagged and killed but the original article remains up.

I like the concept, a risk map could be useful in some circumstances but I absolutely hate the UI design; it reeks of AI with no human thought or care put into it.

Or you could, you know, read the changes your approving