GitHub only
Review a pull request with Devin Review
You open a pull request that has bugs in its refund and webhook code, and Devin Review comments on the lines at fault with suggested fixes.
Steps
- Enter your GitHub user or org. The links and the prompt on this page use it.
- Create your own copy of the starter repo. Open GitHub's new-repository page for devin-demo-pr-review, choose your account as the owner, keep the name
devin-demo-pr-review, and click Create repository.Before you click Create repository, turn on Include all branches. The pull request you review in this lab lives on thefeat/refunds-and-webhooksbranch, and it isn't copied otherwise. - Make sure Devin can access the new repo under Settings → Connections → GitHub.
- Open the pull request that Devin will review. Go to github.com/<you>/devin-demo-pr-review/pull/new/feat/refunds-and-webhooks on GitHub. That page shows the changes on the
feat/refunds-and-webhooksbranch of your copy. Click Create pull request. - Enter the number GitHub gave the new pull request. Then start a session at app.devin.ai and paste the prompt below.
Prompt
Run Devin Review on https://github.com/<you>/devin-demo-pr-review/pull/1 ("refunds and webhooks"). I want a security- and correctness-focused review: money handling, webhook authentication, timing attacks, and anything that could let someone refund more than they paid. Post the findings as review comments on the PR with suggested fixes, ranked by severity, and summarize the top issues here. Don't merge.
What to watch
- Review checks the PR against the rules in the README, not just style.
- Comments are inline on the exact lines, ranked by severity.
You're done when
- The PR has ranked inline comments with suggested fixes.
- Nothing was merged.
Go further
Open your own PR on this repo and run Devin Review on it.