Skip to main content

Update Prethink context (with AI)

io.moderne.prethink.UpdatePrethinkContextStarter

Generate Moderne Prethink context files with AI-generated code comprehension, test coverage mapping, dependency inventory, and FINOS CALM architecture diagrams. Maps tests to implementation methods and optionally generates AI summaries of what each test verifies when LLM provider is configured.

Recipe source​

GitHub: UpdatePrethinkContextStarter.java, Issue Tracker, Maven Central

info

This recipe is composed of more than one recipe. If you want to customize the set of recipes this is composed of, you can find and copy the GitHub source for the recipe from the link above.

This recipe is available under the Moderne Source Available License.

Options​

TypeNameDescriptionExample
StringproviderOptional. LLM provider for generating test summaries: openai, gemini, or poolside.poolside
StringapiKeyOptional. API key for the LLM provider.ps-...
StringmodelOptional. Model name to use for generating test summaries.Malibu-v2.20251021
StringbaseUrlOptional. Custom base URL for the LLM provider.https://divers.poolsi.de/openai/v1/
IntegerrequestsPerMinuteOptional. Rate limit for LLM requests.60

Definition​

  • Find project metadata
  • Find service endpoints
  • Find database connections
  • Find external service calls
  • Find messaging connections
  • Find server configuration
  • Find data assets
  • Find deployment artifacts
  • Find security configuration
  • Find service components
  • Extract coding conventions
  • Extract error handling patterns
  • Extract dependency usage patterns
  • Export context files
    • displayName: Coding Conventions
    • shortDescription: Naming patterns, import organization, and coding style
    • longDescription: Detected coding conventions including naming patterns (class suffixes, method prefixes), import organization, and documentation coverage. Use this to write code that matches the existing style of the codebase.
    • dataTables: [org.openrewrite.prethink.table.CodingConventions]
  • Export context files
    • displayName: Error Handling
    • shortDescription: Exception handling strategies and logging patterns
    • longDescription: Error handling patterns detected in the codebase including try-catch usage, exception types, handling strategies (log, rethrow, wrap, recover), and logging frameworks. Use this to handle errors consistently with existing patterns.
    • dataTables: [org.openrewrite.prethink.table.ErrorHandlingPatterns]
  • Export context files
    • displayName: Library Usage
    • shortDescription: How external libraries and frameworks are used
    • longDescription: Patterns of how external libraries are used throughout the codebase. Shows which classes are commonly imported from each library and typical usage patterns. Use this to use libraries consistently with existing code.
    • dataTables: [org.openrewrite.prethink.table.DependencyUsage]
  • Find CALM relationships
  • Comprehend code with AI
    • provider: poolside
    • model: Malibu-v2.20251021
  • Export context files
    • displayName: Code Comprehension
    • shortDescription: AI-generated descriptions for classes and methods
    • longDescription: AI-generated descriptions of classes and methods. Use this to quickly understand what code does without reading every line. Particularly helpful for unfamiliar parts of the codebase.
    • dataTables: [io.moderne.prethink.table.MethodDescriptions, io.moderne.prethink.table.ClassDescriptions]
  • Find test coverage mapping
    • provider: poolside
    • model: Malibu-v2.20251021
  • Export context files
    • displayName: Test Coverage
    • shortDescription: Maps test methods to implementation methods they verify
    • longDescription: Maps test methods to the implementation methods they exercise. Use this to find existing tests for code you're modifying, understand what behaviors are already tested, and identify gaps in test coverage. When an LLM provider is configured, includes AI-generated summaries of what each test verifies.
    • dataTables: [io.moderne.prethink.table.TestMapping]
  • Dependency report
    • scope: TestRuntime
    • includeTransitive: true
    • validateResolvable: false
  • Export context files
    • displayName: Dependencies
    • shortDescription: Project dependencies including transitive dependencies
    • longDescription: Complete dependency tree including transitive dependencies. Use this to understand what libraries the project uses and avoid suggesting dependencies that conflict with existing ones.
    • dataTables: [org.openrewrite.java.dependencies.table.DependencyListReport]
  • Update Prethink context
  • Generate architecture mermaid diagram

Usage​

This recipe has no required configuration options. It can be activated by adding a dependency on org.openrewrite.recipe:rewrite-prethink in your build file or by running a shell command (in which case no build changes are needed):

  1. Add the following to your build.gradle file:
build.gradle
plugins {
    id("org.openrewrite.rewrite") version("latest.release")
}

rewrite {
    activeRecipe("io.moderne.prethink.UpdatePrethinkContextStarter")
    setExportDatatables(true)
}

repositories {
    mavenCentral()
}

dependencies {
    rewrite("org.openrewrite.recipe:rewrite-prethink:0.2.2")
}
  1. Run gradle rewriteRun to run the recipe.

See how this recipe works across multiple open-source repositories​

Run this recipe on OSS repos at scale with the Moderne SaaS.

The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.

Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.

Data Tables​

Source files that had results​

org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

Column NameDescription
Source path before the runThe source path of the file before the run. null when a source file was created during the run.
Source path after the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Parent of the recipe that made changesIn a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.
Recipe that made changesThe specific recipe that made a change.
Estimated time savingAn estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.
CycleThe recipe cycle in which the change was made.