Code Examination
Purpose
Understand local code before changing it.
When to Use
Use before implementation, refactoring, test fixes, or architecture changes.
Inputs
Entry points, neighboring files, tests, interfaces, naming conventions, ownership boundaries.
Steps
- Locate the relevant code path.
- Read nearby patterns and tests.
- Identify contracts and boundaries.
- Make the smallest compatible change.
Gates
The change matches local style and contracts.
Evidence
Relevant files read and patterns followed.
Anti-Patterns
Inventing a new abstraction without reading the codebase.
Related
project-rules-first, generated-code-review