Tools
This week, we shipped @QodoAI Findings. It's the natural next step from PR-by-PR review. Here's the problem it solves. If you manage an engi…
This week, we shipped @QodoAI Findings. It's the natural next step from PR-by-PR review. Here's the problem it solves. If you manage an engineering team right now, you can probably answer a question a
This week, we shipped @QodoAI Findings. It's the natural next step from PR-by-PR review. Here's the problem it solves. If you manage an engineering team right now, you can probably answer a question about any single pull request your team shipped this week. What you likely cannot answer, at least not quickly, is the version of that question that spans your whole org. > How many issues were caught and fixed across our repos this month? > Which services are accumulating the most risk? > Is review quality on the payments team improving or sliding? > Are the same issues getting flagged for the same reasons over and over? These are the questions that come up in staff meetings, even in board prep these days, in conversations with security... Answering them used to mean stitching together Slack threads, asking around, or pulling a spreadsheet by hand. Qodo Findings, consolidates every issue Qodo has surfaced across your reviewed pull requests into one view. Three parts that work together. A top row of analytics: total critical findings, percentage resolved, average findings per PR. Volume, throughput, trend. The high-level read without having to open anything. Filters underneath: by repo, by owner, by issue type. Cut the data the way you actually need it. Pull up only security findings. Look at a single team. Focus on one service. A full searchable, sortable list of every issue, with the ability to drill straight into the underlying PR when something stands out. Available now in beta on GitHub, GitLab, BitBucket, and Azure DevOps. Would love to get any feedback even DM me! Taking a step back. The point isn't a new dashboard. The point is that the review layer has to operate at a different altitude now. PR-by-PR is necessary, but it isn't sufficient. When code is being generated continuously across teams and repos, leaders need to see across teams and repos. The same way they see across any other part of their operation. This is the first release in that direction. More coming. We care about the software health as a whole, not only PR-by-PR, and there is a lot of innovation needed here. Read more: https://www.qodo.ai/blog/introducing-findings-page/
Source: Itamar Friedman (X) | 2026-05-22