Review a pull request alongside the code it affects
Connect the repository and specify a branch or diff. Gryphon can trace changed calls, inspect error handling and find missing tests.
Example: retries added to an API client
A pull request changes retries and error handling. You need to know whether a retry could create duplicates.
- Find the methods that use the client and the operations they perform.
- Check timeouts, retry counts and duplicate prevention.
- Reference the code for any bug found and add a test if it can be run.
What you get
Pull request findings with code references and check results.
Follow the effects of the change
Ask it to read callers, data formats and failure paths. A retry may be safe for a read and dangerous when creating a payment.
Ask for specific findings
Each issue needs a file, line, triggering conditions and consequences. List assumptions that could not be checked separately.
Verify the finding
Reproduce the case or run a suitable test. Before merging a fix, inspect its diff and command output.
Try it on your own task
Open Web and describe the task. Connect Desktop for files and commands on your computer.