feat: Add `sentry review` command for AI-powered code review
@MathurAditya724 ya está trabajando en esto.
Desde el 3/2/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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)
- Lenguaje dominante
- TypeScript
- Estrellas
- 121
- Forks
- 14
- Merge medio
- 23 h 54 min
- PR fusionados (30 d)
- 103
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de getsentry/cli
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
-
bug jared
-
jared
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
Todos los issues de getsentry/cli
Issues similares
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
Mend: dependency security vulnerability untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100