feat: Add `sentry review` command for AI-powered code review
@MathurAditya724 is already working on this.
Since Feb 3, 2026.
Assessment
This issue has not been assessed yet.
Description
Summary
Add a sentry review command that uses Sentry's Seer AI to review code for bugs, logic errors, and issues that could cause production failures.
Why Before the PR?
The key insight: catch problems before you push, not after.
When you create a PR:
- CI pipelines spin up (costs time and resources)
- Teammates get notified
- Failed checks create noise and delay
With sentry review, you can run a quick AI-powered check locally and fix issues before creating the PR. Ship cleaner code on the first push.
Command Design
# Review current branch changes (vs main)
sentry review
# Review specific PR
sentry review --pr 123
# Review a file or directory
sentry review src/handlers/
# Review staged changes only
sentry review --staged
What It Catches
- Logic errors - Bugs and flawed control flow
- Error-prone patterns - Code likely to cause production failures
- Performance issues - Regressions or inefficient code
- Security concerns - Potential vulnerabilities
Key Differentiator
Unlike generic linters, Seer combines:
- Error context - Historical production errors from Sentry
- Performance data - Real issues your app has experienced
- Code analysis - Static examination of changes
This surfaces issues that will actually cause production problems, not pedantic style nits.
Technical Details
- Use Seer API endpoint for code review
- Integrate with GitHub PR context when available
- Output actionable suggestions with file:line references
- Support both interactive and CI modes
References
- Product page: https://sentry.io/product/seer/ai-code-review/
- Similar to existing Seer commands (
sentry issue explain,sentry issue plan)
- Dominant language
- TypeScript
- Stars
- 121
- Forks
- 14
- Avg merge
- 22h 3m
- Merged PRs (30d)
- 94
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
bug jared
-
jared
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100