code-review-five-axis

Run the five-axis checklist against your diff: verify correctness against the spec, check readability and naming, confirm architecture layering, audit security items like auth checks and input validation, and look for performance issues such as N+1 queries. Report findings by severity before committing.

A thorough checklist covers five areas: correctness (edge cases, error paths, concurrency), readability (naming, function size, comments explaining why), architecture (layering, dependency direction, DI), security (secrets, validation, authorization), and performance (pagination, indexes, memory disposal).

Yes, the checklists include Flutter and Firestore specific items such as const constructors, ListView.builder, stream disposal, Firestore compound query indexes, and avoiding full-collection reads. It also covers TypeScript and Cloud Functions concerns like cold starts and zod validation.

Use this five-axis review for fast self-checks before commits and PR reviews, typically a 5 to 15 minute pass. For stakeholder-facing deep audits with scoring criteria and formal reports, use a dedicated detailed feature review skill instead.

Common anti-patterns include approving without reading carefully, bikeshedding naming while critical bugs remain unresolved, suggesting full module rewrites in small PRs, and blocking merges over personal style preferences. Focus on severity-ranked issues that affect correctness and security first.