GitHub code reviewon pull requests
Connect your repos, run AI code reviews on pull requests, and keep feedback next to the diff. Use the web app for ad-hoc runs, wire GitHub OAuth and webhooks for repo events, or drop in the Action so CI and humans see the same quality bar.
Integration
Built around how you ship on GitHub
OAuth connects your GitHub account to CodeCritic. From there you choose which repositories participate, how reviews are triggered (PR events, manual runs, or Action workflows), and how results surface - in the product, on the PR, or both. Exact capabilities depend on your plan - see Pricing and the User guide for step-by-step setup.
Reviews on your PRs
Connect a repository and run AI reviews where your team already discusses code. Feedback is tied to the diff so context stays next to the change.
PR comments
Summaries and findings can be published back to the pull request so human reviewers see AI output alongside their own notes - less back-and-forth in chat.
GitHub Action
Automate runs in CI with the official Action: trigger on push or pull_request, reuse the same review engine as the web app and REST API.
Webhooks
Incoming webhooks tie pushes and PR events to review jobs so automation matches how your repo already moves - configure what your plan supports.
REST API
The same analysis pipeline powers HTTP APIs for custom pipelines - useful when you wrap CodeCritic into internal tools or release automation.
Org-friendly
As you add repos and members, company billing and workspace controls scale with you - see the teams page for how orgs map to subscriptions.
Typical flow
From signup to review on a PR
- 1
Create a workspace
Sign up for CodeCritic and open Settings. Your workspace is where reviews, API keys, and GitHub links live.
- 2
Connect GitHub
Authorize via OAuth and pick repositories you want to analyze. You stay in control of scope and can revisit access anytime.
- 3
Trigger a review
Run from the dashboard, from a webhook when a PR opens or updates, or from the GitHub Action in a workflow file.
- 4
Ship with context
Read structured findings in CodeCritic and, where configured, on the PR thread - so reviewers agree on what changed before merge.
Why teams use it
Automation without losing the human thread
AI code review on GitHub is not a replacement for your team - it is a fast first pass that catches risky patterns, missing edge cases, and style drift before humans spend time on line-by-line debate. CodeCritic groups issues by theme and severity so triage stays readable even when the diff is large.
Because the same engine backs the browser, API, and GitHub paths, you do not maintain two different quality bars. Developers can paste a snippet in the web UI for a quick check, while release branches stay on the PR workflow your managers already trust.
For compliance-minded orgs, access is explicit: connect only the repos you need, use company billing when you are ready, and pair the product with 2FA and API key rotation in Settings. Data handling is described in Privacy.
When you outgrow a single maintainer, move to shared plans and the teams story - same GitHub integration, clearer ownership of who pays and who can run reviews.
What you need to know
- Permissions: you choose which repositories are connected; we use GitHub access only to fetch code and post feedback you configure (see Privacy).
- Same engine everywhere: browser paste, webhook, Action, or API - one pipeline. Deep links to setup live in Help.
- Teams: shared billing and member management when you outgrow a solo account - AI code review for teams.
FAQ
GitHub code review with CodeCritic
Short answers - full procedures are in the user guide.
Run a GitHub code review with CodeCritic
Sign up, connect GitHub from Settings, and route reviews through the path that fits your team - dashboard, webhook, or Action.