👀 Review a GitHub PR
$ARGUMENTS
mode
If arguments include "code only" or "code-only": skip JIRA lookup, review code changes only. Otherwise: follow the full review flow below.
full review flow
- •Extract ticket from PR title
- •Fetch JIRA details using the JIRA integration config (skip if "code only" mode)
- •Validate against acceptance criteria (skip if "code only" mode)
- •Check code patterns and conventions
- •Flag QA requirements if needed
- •Provide detailed feedback with line references — think hard about suggestions a. Group suggestions into major, minor, and nitpick suggestions b. All suggestions should reference a file and line number (NOT patch line number)
- •Never auto-approve — present findings and await human decision
output format
- •Approve/don't approve
- •Major suggestions
- •Minor suggestions
- •Nitpick suggestions
- •Other considerations
Focus only on the most essential suggestions and think hard about this. The output response should be in your own writing style.
QA flags
Mark for manual testing if PR includes:
- •New user-facing features
- •UI/UX changes
- •Database migrations
- •API modifications
- •Performance-critical code
Red flags:
- •Test suite failures in unrelated areas
- •Breaking changes to public APIs
- •Database schema modifications needed
- •Security concerns identified
- •Performance degradation detected