Review a PR for functional correctness and project conventions. Focus on logic, architecture, and behavior. Formatting issues are caught by CI (ruff, pre-commit) and do not need manual review.

Steps

1. Load PR context

gh pr view $ARGUMENTS --json title,body,files,additions,deletions
gh pr diff $ARGUMENTS

2. Validate PR title and description

Title matches Conventional Commits regex, under 72 chars
Description sections meet word minimums (Summary 5w, Description 10w, Tests 10w)
These are also CI-enforced, so flag only if CI somehow missed them

3. Review functional changes

Focus on:

Logic correctness: does the code do what the PR claims?
Edge cases: are error paths handled?
API changes: are they backwards compatible or properly marked as breaking?

Review a PR for functional correctness and project conventions. Focus on logic, architecture, and behavior. Formatting issues are caught by CI (ruff, pre-commit) and do not need manual review.

Steps

1. Load PR context

gh pr view $ARGUMENTS --json title,body,files,additions,deletions
gh pr diff $ARGUMENTS

2. Validate PR title and description

Title matches Conventional Commits regex, under 72 chars
Description sections meet word minimums (Summary 5w, Description 10w, Tests 10w)
These are also CI-enforced, so flag only if CI somehow missed them

3. Review functional changes

Focus on:

Logic correctness: does the code do what the PR claims?
Edge cases: are error paths handled?
API changes: are they backwards compatible or properly marked as breaking?

Review Pr

Steps

1. Load PR context

2. Validate PR title and description

3. Review functional changes

Review Pr

Steps

1. Load PR context

2. Validate PR title and description

3. Review functional changes

5. Check scope

6. Check test coverage

Output

Feishu Perm

Logistics Exception Management

Review

Employment Contract Templates

On-Call Handoff Patterns

Advogado Criminal