Show HN: Stage – Putting humans back in control of code review(stagereview.app)
8 pointsby cpan227 hours ago4 comments
  • sscarduzio3 hours ago
    We have the same problem, and I came up with this:

    https://sscarduzio.github.io/pr-war-stories/

    Basically it’s distilling knowledge from pr reviews back into Bugbot fine tuning and CLAUDE.md

    So the automatic review catches more, and code assistant produces more aligned code.

    • cpan223 hours ago
      This is really cool and we definitely have this problem as well. I really like the flowchart deciding on where to put each learning. Will have to try it out!

      Do you find that this list of learnings that end up BUGBOT.md or LESSONS.md ever gets too long? Or does it do a good job of deduplicating redundant learnings?

  • gracealwan3 hours ago
    Totally different part of the reviewing experience, but I would love to see PR comments (or any revisions really) be automatically synced back to the context coding agents have about a codebase or engineer. There’s no reason nowadays for an engineer or a team of engineers to make the same code quality mistake twice. We manually maintain our agents.md with codebase conventions, etc, but it’d be great not to have to do that.
    • dean_stratakos3 hours ago
      100%. A big part of code review in my mind is to automate away specific mistakes and anti-patterns across a team. I think there are a lot of interesting things to be done to merge the code writing and code reviewing cycles.
  • 7 hours ago
    undefined
  • ryanjso7 hours ago
    I like the chapters thing, a lot of PRs I review should really be like 5 prs so its nice to have it auto split like that.

    Do you see a world where it splits them up on the git level?

    • dean_stratakos6 hours ago
      Yeah that could be useful, especially with the increased popularity of stacked PRs

      But I see it working together with chapters, not instead of bc it's still good to see the granularity within a PR