Show HN: I built a tool to assist AI agents to know when a PR is good to go

3 comments

• rootnod32 hours ago
  Sorry, so the tool is now even circumventing human review? Is that the goal?<p>So the agent can now merge shit by itself?<p>Just the let damn thing push nto prod by itself at this point.
  • baxtr1 hour ago
    I’m not saying this is, but if I were a malicious state actor, that’s exactly the kind of thing I’d like to see in widespread use.
  • ljm1 hour ago
    Someone’s gonna think about wiring all this up to Linear or Jira, and there’ll be a whole new set of vulnerabilities created from malicious bug reports.
  • literalAardvark1 hour ago
    In some workflows it&#x27;s helpful for the full loop to be automated so that the agent can test if what&#x27;s done works.<p>And you can do a more exhaustive test later, after the agents are done running amok to merge various things.
  • danenania1 hour ago
    I don’t think “ready to merge” necessarily means the agent actually merges. Just that it’s gone as far as it can automatically. It’s up to you whether to review at that point or merge, depending on the project and the stakes.<p>If there are CI failures or obvious issues that another AI can identify, why not have the agent keep going until those are resolved? This tool just makes that process more token efficient. Seems pretty useful to me.
• joshuanapoli1 hour ago
  This looks nice! I like the idea of providing more deterministic feedback and more or less forcing the assistant to follow a particular development process. Do you have evidence that gtg improves the overall workflow? I think that there is a trade-off between risk of getting stuck (iteration without reaching gtg-green) versus reaching perfect 100% completion.
• mcolley8 hours ago
  Super interesting, any particular reason you didn&#x27;t try to solve these prior to pushing with hooks and subagents?
  • dsifry8 hours ago
    I did! The issue however, is having a clear, deterministic method of defining when the code review was &#x27;done&#x27;. So the hooks can fire off subagents, but they are non-deterministic and often miss vital code review comments - especially ones that are marked in an inline comment, or are marked as &#x27;Out of PR Scope&#x27; or &#x27;Out of range of the file&#x27; - which are often the MOST important comments to address!<p>So gtg builds all of that in and deterministically determines whether or not there are any actionable comments, and thus you can block the agent from moving forward until all actionable comments are thoroughly reviewed, acted upon or acknowledged, at which point it will change state and allow the PR to be merged.
    • blutoot2 hours ago
      I thought hooks are always fired if you use it as a PreToolUse event. Wouldn’t that work for the GitHub action tools from the GitHub mcp?