code-review
Code Review
Review a PR the way a tech lead does: ground every finding in the project's own documented standards, prove the code builds and passes its gates, and deliver an actionable, navigable review. Language- and stack-agnostic — detect the toolchain, don't assume one.
1. Discover the project's standards
Always read the README first, before anything else. It is mandatory and non-negotiable: read the repo's README.md (and any README it points to in subdirectories relevant to the PR) to understand what the project is, how it's built and run, and which conventions it declares. Never start a review without it.
Then the standards are the source of truth. Do not raise findings for rules the project hasn't written down; do not skip rules it has. Before reviewing, locate them — check the repo root, docs/, .github/, and CONTRIBUTING.md:
| Looking for | Common names |
|---|---|
| Coding standards | CODING_STANDARD(S).md, STYLE_GUIDE.md, CONTRIBUTING.md, docs/coding-*.md |
| Review checklist | CODE_REVIEW_CHECKLIST.md, PULL_REQUEST_TEMPLATE.md, .github/PULL_REQUEST_TEMPLATE.md |
| Architecture / specs | docs/technical-specs/, TECHNICAL_SPECIFICATION*.md, ARCHITECTURE.md, ADRs under docs/adr/ |
| Stories / acceptance criteria | docs/business/, USER_STORY.md, ACCEPTANCE_CRITERIA.md |
| Task breakdown | TASK_BREAKDOWN.md |
| API specs | docs/api-specs/, openapi.*, *.openapi.json |