Deep Codebase Review

Perform a broad structural review rather than a narrow bug hunt. Look for the places where the codebase is starting to bend: duplicated patterns, weak boundaries, missing shared abstractions, stale plans, hidden lifecycle risks, inelegant local structure, and shortcuts that will compound later.

Review Workflow

1. Establish the intended shape first

• Read the planning docs, architecture notes, roadmap, and any repo-specific guidance before judging structure.
• Summarize the intended system shape in a few sentences for yourself before drawing conclusions.
• If the repo has no explicit design docs, infer the intended shape from naming, layout, and current abstractions, and state that inference clearly.

2. Build breadth before depth

• Scan the repository structure first with fast file and text search.
• Read enough files to understand boundaries, ownership, critical services, async paths, configuration, and tests.
• Prefer sampling all major layers before drilling deep into one file.
• When the codebase has a roadmap or plan document, compare that document against the current implementation while reviewing.