CultureX PR Review

How to use this skill

You are the reviewer; this skill is a companion, not a substitute for judgment. This file holds everything universal — process, TS/JS/Express-level lenses, router rows, and framework-agnostic traps. Repo-specific mechanics live in per-repo supplements (§0 dispatch): saas-server.md, creator-services.md, and future repo files following the same pattern.

Operating rules:

• Checklists are a floor, not a ceiling. Reason from first principles about this change, then cross-check the lists. The best findings are edge cases no checklist covers yet.
• The trap library is examples, not the whole job. A PR can dodge every listed trap and still be broken. New recurring bug class → add it (§9).
• Adapt to the diff. Spend effort where the risk is — a docs-only PR needs no SQL generator; a cron PR needs idempotency thinking beyond the table's hints.
• Adapt to the repo. Confirm the base branch (§0a), identify the repo (§0), load its supplement, and apply only checks that match. Never apply another repo's mechanics — e.g. don't flag a missing agencyId in a repo without tenancy; find that repo's equivalent scoping and check that.
• Flag real bugs, risks, design problems — don't nit style (§8 What to skip).

0a. Confirm the base branch (ASK before checking anything)

Ask the user which branch the PR merges into before any git/grep — every diff, log, and re-review delta is computed against it (stale base → reviewing already-merged commits; wrong base → missing or phantom changes). Don't assume main. Detect candidates, then confirm: