# Retrofit GRAPHQL Build Dependencies > Understand and change retrofit-graphql build logic, module dependencies, version catalog entries, Dokka setup, and shared Gradle conventions. Use for buildSrc edits, new dependencies, or documentation pipeline work. Use when this capability is needed. - Skill: `tomevault-io/retrofit-graphql-build-dependencies` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/retrofit-graphql-build-dependencies` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/retrofit-graphql-build-dependencies/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: DevOps & Infra - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/retrofit-graphql-build-dependencies --- # Retrofit GraphQL Build And Dependencies ## What This Skill Produces - A safe path for changing module dependencies or shared build logic. - A map of where versions, plugins, Dokka, Spotless, and Android defaults are defined. - Clear guidance on whether a change belongs in a module build file, the version catalog, or `buildSrc`. ## When To Use - Adding or upgrading dependencies. - Changing module relationships. - Editing Dokka, Spotless, JDK, Android, publishing, or test conventions. - Understanding how the converter, annotation, discovery, and model packages are wired. ## Procedure 1. Read the [build map](./references/build-map.md) to find the owning file for the convention you want to change. 2. If the change introduces or upgrades a dependency, add the version and alias in `gradle/libs.versions.toml` first. 3. If the behavior should apply to both modules, implement it in `buildSrc` instead of duplicating it in both `build.gradle.kts` files. 4. Remember that `:app` is excluded from the Gradle build when the `CI` environment variable is set; only `:library` is built and tested in CI. 5. Keep Dokka, Spotless, and test behavior aligned with the shared configuration in `buildSrc`. 6. When running Gradle locally, use the existing `jenv-gradle-low-ram` skill if Java selection or memory pressure becomes an issue. ## References - [build map](./references/build-map.md) --- > Source: [AniTrend/retrofit-graphql](https://github.com/AniTrend/retrofit-graphql) — distributed by [TomeVault](https://tomevault.io).