> ## Documentation Index
> Fetch the complete documentation index at: https://palmier.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Review Pull Requests

> Get expert code reviews on every PR to catch issues and maintain quality standards

# Review Pull Requests

When you open a PR, trigger the PR Review agent to get comprehensive feedback on your code changes. The agent acts like a staff engineer reviewer, catching architectural issues, suggesting improvements, and ensuring your code integrates well with the existing codebase.

<img src="https://mintcdn.com/palmier/uwIa6OlcEeHikIKc/images/screenshot_pr_review.png?fit=max&auto=format&n=uwIa6OlcEeHikIKc&q=85&s=2e836fe901d98ab223d9b5b350f5cb80" alt="PR Review Agent in action showing detailed code feedback" width="1402" height="706" data-path="images/screenshot_pr_review.png" />

## Expert Review Capabilities

* **Architectural Consistency**: Ensures code changes align with existing architecture and design patterns
* **Separation of Concerns**: Validates proper responsibility isolation and code organization
* **Design Simplicity**: Identifies overcomplicated solutions and suggests simpler alternatives
* **Functional Correctness**: Verifies features work as intended with comprehensive testing
* **Error Handling & Edge Cases**: Reviews error conditions and boundary case coverage
* **External Integration Safety**: Checks timeouts, retries, and error handling for external calls

## Structured Review Process

1. **Context Analysis**: Examines codebase architecture, patterns, and existing conversations
2. **Comprehensive Review**: Uses design review tools to analyze against 12 quality criteria
3. **Issue Validation**: Verifies all suggestions are accurate and actionable
4. **Strategic Feedback**: Selects top 3 highest-priority issues with clear solutions
5. **Formatted Comments**: Provides GitHub-style reviews with file links and specific recommendations

## When to Use

* **Before merging any PR**: Get a second pair of eyes on your changes
* **For junior developers**: Learn best practices through detailed feedback
* **Complex features**: Ensure architectural consistency with existing code
* **Critical code paths**: Extra validation for important system changes
* **Team standards**: Maintain consistent code quality across your team
