Review Ruby/Rails/Grape Code

Review changed code by spawning specialist agents. Review is read-only - never fix during review.

Review Philosophy

Reviews catch issues before they reach production. Each specialist focuses on their domain:

• Correctness: Does it work? Handle edge cases?
• Security: Are there vulnerabilities? Input validation?
• Maintainability: Can others understand and modify this?
• Performance: Will it scale? Any N+1s?
• Style: Does it follow conventions?

Collecting Changed Files

Resolve the base ref before spawning reviewers: