newcomer-lens-review

Review as a competent engineer who just joined: general engineering knowledge, but no project-specific context — design decisions, domain terms, historical constraints, team conventions.

Steps

1. Read the diff or files. Mark every point where understanding requires information not present in the code.
2. Categorize each gap (see "Gap categories" below).
3. Produce findings first using the output contract below.
4. Prioritize: top 3 gaps that most need documentation.

Context boundary

Assumed: language semantics, common algorithms, industry standard patterns. Not assumed: why this approach, project terminology, past attempts, implicit requirements, domain concepts.

Gap categories