Ship faster.
Stop waiting.
Every pull request now gets a fast AI review. Fix what matters, reply to what you disagree with, then send it to your tech lead for the final review.
Test locally
Make sure the feature works on your machine. Try the main flow and a few edge cases.
Hover for more- Test the main flow from start to end
- Try a few edge cases too
- Make sure the tests pass on your machine
- If it does not work for you, the AI cannot help
Open the PR
Push your branch. The AI starts on its own with every new commit.
Hover for more- Starts when you open, reopen, push to, or mark the PR ready
- Draft PRs are skipped until you mark them ready
- The first run usually finishes in under a minute
- Adds one summary comment at the top of the PR
Iterate fast
Fix the code, or reply to the comment. Push again. The AI checks again.
Hover for more- FIX: change the code and push. The AI marks the comment as resolved.
- REPLY: when the AI is wrong, reply in the comment thread and say why. The AI treats it as handled.
- ASK KEVIN: tag your tech lead in the thread for hard decisions.
- The summary at the top is rewritten on every push, so the PR stays clean.
Final review
When the AI is happy and you are happy, the tech lead does the final review and merges.
Hover for more- Summary should say TIP, or WARNING with a reply on each item
- Do not send it for review if a sensitive file shows CAUTION
- Write a short PR description so reviewers know what to look at
- Tech lead does the final review and decides on merge
Three status signals
Looking good
No serious issues. Ready to send to your tech lead for the final review.
Worth a look
Some things to look at or reply to before merge.
Likely blocker
Fix it or reply to it before you ask your tech lead to review.
Who does what
The AI
- Runs on every push, takes seconds
- Posts one summary at the top, updated on every push
- Adds a few comments on specific lines
- Closes old comments once they are fixed
- Never edits your code, never blocks the merge
You
- Test the feature on your machine before pushing
- Decide what is worth fixing and what is not
- Reply to the comment when you think the AI is wrong
- Keep the PR to one change at a time
- Send it to your tech lead when the review is clean
Three ways to answer a comment
Make the change
Push the fix. The AI will close the comment on the next run.
Reply in the thread
Say why the AI is wrong, or why it is not part of this PR. The AI treats it as done.
Ask the lead
For hard decisions. The tech lead will weigh in during the final review.
Rules of the road
Do
- Test the feature on your machine before opening the PR
- Keep PRs small. One change per PR.
- Reply in the thread when you disagree with the AI
- Push your fixes and let the AI review again
- Send it to your tech lead only when the AI review is clean
Don't
- Open a PR you have not tested on your machine
- Mix bug fixes and refactors in the same PR
- Add style or formatting changes that are not part of the task
- Close a comment thread without replying
- Wait on review to find the obvious issues
PR size matters
One change. One purpose.
Focused change. Easy to review. The AI is more useful.
Five changes mixed together.
Bug fix plus refactor plus formatting. Slow to review. Hard to undo.
Faster PRs. Across time zones. Less waiting on each other.
AI helps with the first pass · Humans still own the final review and merge