> ## Documentation Index > Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt > Use this file to discover all available pages before exploring further. # Repository Intelligence > Ground FORGE planning, generation, and repair in the structure and conventions of an existing repository. # Repository Intelligence Repository Intelligence gives FORGE structured awareness of an existing codebase before it plans or changes software. Without repository context, an AI can only infer architecture from whatever files happen to be pasted into a prompt. With repository intelligence, Starfire can reason from a broader project snapshot. ## What it can inform Repository-aware workflows can use information such as: * file and directory structure * package or dependency manifests * framework configuration * imports and module boundaries * naming patterns * existing implementation examples * tests and validation commands * repository documentation ## Retrieval over full-repository injection Large repositories cannot be treated as one prompt. Starfire can search or retrieve relevant files and regions based on the current task while retaining higher-level repository metadata. ## Change planning Before modifying a repository, FORGE can use repository context to identify the likely change surface. For example, a request to add a billing capability might require changes across an API module, database model, validation DTO, web UI, tests, and documentation. Repository intelligence helps the planner locate those surfaces before editing. ## Repair workflows When validation reports an error, repository context helps the repair engine understand whether the fix belongs in the failing file or in a related type, import, configuration, or dependency elsewhere in the project. ## Source revision A repository-backed build should be associated with the source state it inspected. If the repository changes significantly after context was prepared, refresh the source before assuming the previous analysis still applies. ## Access control Starfire should only read repository material that the connected integration and active project are authorized to access. Credentials belong in the integration layer and must not be placed into prompts or build files. See how repositories also operate as a persistent Knowledge source outside FORGE.