Automatic Reviews
Jasper automatically reviews every pull request, providing comprehensive feedback within minutes.
How It Works
When a pull request is opened or updated, Jasper automatically:
- Analyzes the diff - Reviews all changed files and lines
- Evaluates the code - Uses Claude AI to assess quality, security, and best practices
- Posts a review - Submits a GitHub review with findings and verdict
- Adds inline comments - Comments on specific lines that need attention
What Gets Reviewed
Jasper examines your code for:
Code Quality
- Readability and clarity
- Naming conventions
- Code structure and organization
- DRY principle violations
Security
- Injection vulnerabilities
- Authentication issues
- Data exposure risks
- Insecure configurations
Performance
- Inefficient algorithms
- N+1 query issues
- Memory concerns
- Unnecessary operations
Best Practices
- Language idioms
- Framework patterns
- Error handling
- Edge cases
Review Verdicts
Each review concludes with one of three verdicts:
| Verdict | Meaning |
|---|---|
| APPROVE | Code looks good with no significant issues |
| COMMENT | Suggestions for improvement but not blocking |
| REQUEST_CHANGES | Issues that should be addressed before merging |
Review Timing
Reviews are triggered when:
- A pull request is opened
- A pull request is synchronized (new commits pushed)
- A pull request is reopened
Reviews typically complete within 1-3 minutes depending on the size of the changes.
Controlling Automatic Reviews
You can configure automatic reviews per-repository in your repository settings:
- Enable/disable automatic reviews
- Set file patterns to include or exclude
- Configure review sensitivity