Write a guided walkthrough for a complex pull request

Structure complex multi-file pull requests into a clear, numbered narrative review order for your teammates.

You getPR Overview, suggested Review Order and critical Decision Points

Prompt

Prompt
Act as a software engineer preparing a guided review walkthrough for a pull request.
- Analyze the pasted git diff or changed files summary.
- Group related file changes into logical review phases instead of alphabetical file order.
- Provide a recommended reading sequence starting with core data structures or business logic.
- Highlight breaking changes, subtle edge cases, or non-obvious design choices reviewers must inspect closely.
Output format:
1. PR Overview (2-3 sentences summarising the intent)
2. Suggested Review Order (numbered phases with file lists and what to look for)
3. Critical Decision Points (bullets explaining non-obvious trade-offs)
4. Risk & Test Focus Areas (specific scenarios for the reviewer to verify)
Here is the diff or list of changes:

Example output

Example for: Refactoring user subscription tiers across 14 files

1. PR Overview

This PR splits our single enterprise subscription tier into tiered seat allocations and adds usage quotas. It introduces an updated billing schema, updates Stripe webhook handlers, and updates downstream feature flags.

2. Suggested Review Order
  1. Core Data Contracts (src/types/billing.ts, prisma/schema.prisma)

    • Check the new SeatTier enum and ensure fields match the migration script.
  2. Database Migration (prisma/migrations/20240315_add_seat_tiers.sql)

    • Verify default fallback values for existing customer rows.
  3. Domain Business Logic (src/services/billingService.ts)

    • Review the seat allocation calculations and boundary conditions.
  4. External Integrations & Webhooks (src/controllers/stripeWebhook.ts)

    • Verify idempotency keys and error handling for failed charge webhooks.
  5. API & Endpoints (src/routes/billing.ts, src/client/pages/Settings.tsx)

    • Routine presentation changes; verify payload schemas.
3. Critical Decision Points
  • Opted to handle legacy tier conversions synchronously during login rather than run a separate batch backfill script to prevent lock contention on the accounts table.
4. Risk & Test Focus Areas
  • Test upgrading from legacy grandfathered plans with more than 50 seats.
  • Verify behavior when Stripe sends duplicate invoice.payment_succeeded webhook events.
Written by AI from this prompt. Your results will vary.

Paste your git diff --stat or key file diffs directly into ChatGPT, Claude, or Gemini. Paste the generated walkthrough directly into your pull request description or as self-review comments.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Coding