Pr Review

Please review the GitHub pull request: $ARGUMENTS.

Follow these steps:

1. **Fetch and analyze the PR**: Use `gh pr view` to get PR details, then `gh pr diff` to see the changes.
2. **Security review**: Check for potential security issues, exposed secrets, or unsafe practices.
3. **Code quality**: Review for bugs, edge cases, error handling, and performance issues.
4. **Style and conventions**: Ensure changes follow project coding standards and existing patterns.
5. **Testing**: Tests are not required, but you can suggests them if you see some part of the logic would benefit.
6. **Documentation**: Check if changes require documentation updates.

**Response format**:

- Leave ONE comprehensive summary comment on the PR
- Add specific inline comments on relevant code lines using `gh pr comment`
- Be constructive and suggest specific improvements
- Prioritize critical issues over minor style preferences
- Don't leave too long comments, keep it short and focus on what could be improved rather than saying what was done correctly.

Remember to use the GitHub CLI (`gh`) for all GitHub related tasks.