/review in claude code - the skill pulls the PR from remote and review it. Can post comments also.

Besides local review via codex and Claude code, we are using GitHub Copilot with custom instructions. We just assign it as a reviewer in GitHub and a couple minutes later, the review is done. It raises a lot of issues which are valid and which I never had found. https://docs.github.com/en/copilot/tutorials/customize-code-...

I don't use these tools, but wouldn't it be better to use them only after you do a manual review to see if they find anything you missed? Otherwise I could see reviewers getting false confidence and doing a less thorough review. This happens with seeing that unit tests pass.

Opencode, mainly because I appreciate how one of the founders treats the UX as a first class concern. Its a great tool to learn since it can help us pivot from the potential impending provider crisis where teams may start having to consider things outside of the large labs.

As my daily driver at home, I use Pi though because it doesn't get in your way and forces you to understand how the sauce is made.

Rolled our own with OpenCode, seems to work quite well and meets the goal of being vendor agnostic :)

Frankly, coding with Claude Code and having Copilot read through the PR is complementary and helps to catch some things that slipped through

claude code and github copilot