Capability
It checks the change against what was actually asked for.
Code can be written perfectly and still solve the wrong problem. Moonray AI reads the linked ticket, compares what was built against what was requested, and says so when the two do not line up.
What it does
This is the single most useful check a reviewer skips, because doing it properly means opening the ticket, reading it, and holding it in your head while you read the diff. Under queue pressure nobody does that.
We read the ticket and the change together and report the difference: an acceptance criterion nothing in the change addresses, behaviour that was built but never asked for, or an edge case the ticket names and the code does not handle.
PAY-1183 asked for
- done Reject a repeated key with the original response
- done Keys expire after 24 hours
- missing Surface the retry state to the operator
The third acceptance criterion is not addressed by anything in this change. It may be in the linked frontend pull request.
Questions.
Which trackers do you support?
The connection is made at setup. Tell us which one your team uses and we will confirm before you install.
What if a change has no ticket?
The intent check is skipped and listed as not checked in the assessment. Everything else runs.
See it on your own pull requests.
We install on one repository, let Moonray AI assess the next changes your team opens, and go through what it found with you. If the position is not better than what you have now, you will know within a week.
Nothing to host. Reviews begin on the next pull request opened.