Use case · Engineering
A second read on every pull request.
Run /review with a pull request number. Opisense Code reads the description, the diff, the CI checks and the surrounding code, then writes up what it found and what it would change.
- Pull request review
- Diffs
- Skills and plugins
How it works
- 01
Pick the pull request
Run /review with a number, or without one to list open pull requests and choose.
- 02
Name the focus
Add what matters most after the number, such as error handling or migrations.
- 03
Read the review
Get an overview, concerns, edge cases, CI status and a suggested verdict. You decide what to post.
Try asking
Things you can type in Opisense today.
/review 482
/review 482 error handling and database migrations
Review my uncommitted changes and flag anything a reviewer would question.
Questions
Ready to get started?
Start free, or talk with us about the work you want to hand over.