project-context-ingestion

To map a Kotlin Spring Boot repository, inspect Gradle settings, build files, and dependency catalogs to capture module boundaries, framework mode, and version constraints. This produces a concise project brief ensuring proposed code changes align with existing architectural constraints.

Identify module boundaries and framework mode by reading root and module build files alongside the Gradle wrapper configuration. This maps multi-module project architecture, inferring MVC or WebFlux persistence approaches to guide safe, compatible recommendations across the technology stack.

Yes, you can capture Kotlin and Spring Boot version constraints by reading settings.gradle.kts, dependency catalogs, and plugin usage. It records exact Gradle toolchain versions, framework modes, and plugins to verify technology stack consistency across all project modules.

Repository context mapping infers persistence and test stack details by analyzing dependency declarations and plugin configurations within Gradle build files. This mechanism extracts the persistence approach and testing frameworks to guide architecture decisions and ensure safe code modifications.

You need a Gradle wrapper and standard build files like settings.gradle.kts to analyze a Kotlin Spring repository. Reading these configuration files captures toolchain versions, module structures, and dependency constraints required to produce an accurate architecture brief.

Map repository context before planning changes to avoid violating architectural boundaries and version constraints. It records framework mode, modules, and dependencies, ensuring downstream agents generate safe, compatible recommendations that align with the existing technology stack.