implementation-context

To ensure new code matches existing codebase conventions, you can scan 2-3 neighboring files to extract patterns for error handling, naming, imports, and tests, generating a structured note to guide your implementation.

Local code pattern extraction analyzes nearby repository files to summarize conventions and reusable components. It helps when modifying functionality by ensuring new implementations fit the existing codebase rather than just passing tests.

To find reusable utilities and test helpers and avoid code duplication, perform a neighborhood scan of related files to identify existing error definitions and test structures that can be directly reused.

Yes, you can use this pattern extraction approach without executing code. It requires only the ability to access the repository file system to read files and produce a structured note for the agent.

You need to analyze codebase conventions before adding a new operation when you want to align with existing style and reuse code. This prevents introducing inconsistent patterns or duplicating existing utilities.

The best way to summarize error handling and naming conventions is to read 2-3 related files and extract patterns on edge-case handling, imports, and test structures, recording the findings in a concise reference note.