clinical-reasoning: Skill for Claude Code

Creating PRs with Linked Builds

Overview

This project supports linked builds — composite Gradle builds that substitute Maven Central artifacts with local source checkouts of sibling repositories. When creating PRs that span multiple repositories, each PR must declare its cross-repo dependencies using Depends-On: directives so CI can build them together.

Key Files

• local.properties (gitignored): Developer's active linked builds
• local.properties.example: Template showing available linked builds
• build-logic/src/main/kotlin/cqf/LinkedBuild.kt: Registry of all known linked builds (LinkedBuildRegistry) — contains repo slugs, property keys, build roots, and substitution mappings
• build-logic/src/main/kotlin/cqf.linked-builds.settings.gradle.kts: Settings plugin that reads local.properties and calls includeBuild() with dependency substitutions
• build-logic/src/main/kotlin/cqf.ci-conventions.gradle.kts: CI plugin with the resolveLinkedBuilds task that parses Depends-On: from PR descriptions

Workflow

When a developer asks you to create PRs for their linked build changes, follow this procedure. The goal is to create PRs from the most upstream repo down to this repo, with each downstream PR declaring Depends-On: for its upstream dependencies. Once all PRs are created, go back and update the upstream PRs to indicate they block downstream work by appending a Blocks: section.

Step 1: Discover Active Linked Builds

Read local.properties in the project root. Each property key maps to a LinkedBuild entry in the registry. For example:

cql.engine.path=../clinical_quality_language

Look up each active property key in LinkedBuildRegistry (in LinkedBuild.kt) to get the repo slug, build root, etc.

If no linked builds are active (i.e., local.properties doesn't exist, is empty, comments out all properties, or only has unrelated properties), then no cross-repo PRs are needed, exit this workflow, and create a single PR for this repo as usual.