repo-context-gathering

To gather architecture context, scan the repository to detect structural archetypes like VIPER, GraphQL feed, modular SDK, or Bento patterns. This identifies the relevant files and data flow, producing a concise context pack that reduces cognitive load before making codebase edits.

Repo archetype detection identifies whether a repository follows classic VIPER, GraphQL feed, modular SDK, or B2C/Bento module patterns. It helps codebase analysis by collecting only the essential files proving local architecture, ensuring you edit or extend features safely without scanning the entire codebase.

Yes, you can automatically detect VIPER and GraphQL feed patterns by scanning the repository structure. The analysis deduces the local architecture and data flow, outputting a ready-to-use context pack with relevant files and recommended next steps to guide your feature implementation.

The best way to find relevant builder and dependency injection files is to run a context deduction scan for the Bento module archetype. This collects the minimal set of files proving the local architecture and data flow, providing a focused context pack for downstream edits.

Yes, repo context gathering works for modular SDK patterns by detecting the archetype and deducing the minimal architecture context. It outputs relevant files along with guidance for downstream edits and testing, ensuring you can safely extend the SDK feature.