sync-data-relational

2
0
Source

Analyze spring-data-relational version changes and identify required updates for the current project. Use when upgrading spring-data-relational versions or syncing with upstream changes.

Install

mkdir -p .claude/skills/sync-data-relational && curl -L -o skill.zip "https://mcp.directory/api/skills/download/3991" && unzip -o skill.zip -d .claude/skills/sync-data-relational && rm skill.zip

Installs to .claude/skills/sync-data-relational

About this skill

Sync Spring Data Relational Changes

This skill helps synchronize spring-data-relational version updates to the spring-jdbc-plus project.

When to Use

  • When a new spring-data-relational version is released
  • When asked to "sync data-relational changes"
  • When asked to "update to spring-data-relational X.X.X"
  • When analyzing what needs to be updated for a version upgrade

What This Skill Does

  1. Fetches Version Diff: Retrieves changes between two spring-data-relational versions from GitHub
  2. Analyzes Changes: Categorizes changes into:
    • API changes (new methods, deprecated methods, signature changes)
    • Dependency upgrades
    • Bug fixes
    • Documentation updates
  3. Identifies Impact: Searches the current codebase for affected code
  4. Provides Action Items: Lists specific files and changes needed

Instructions

Step 1: Determine Versions

  1. Check gradle.properties to find current springDataBomVersion
  2. Determine the spring-data-relational version from the BOM version
    • Spring Data BOM 2025.0.5 → spring-data-relational 3.5.5
    • Spring Data BOM 2025.0.6 → spring-data-relational 3.5.6
  3. Ask user for target version if not specified

Step 2: Fetch Changes from GitHub

Use WebFetch to get the comparison from: https://github.com/spring-projects/spring-data-relational/compare/{old-version}...{new-version}

Example: https://github.com/spring-projects/spring-data-relational/compare/3.5.5...3.5.6

Step 3: Analyze Changes

Categorize the changes:

Critical Changes (High Priority):

  • API deprecations
  • Breaking changes
  • Signature changes in methods we override/use

Important Changes (Medium Priority):

  • New features we might want to adopt
  • Bug fixes that affect our code
  • Dependency upgrades

Informational (Low Priority):

  • Documentation updates
  • Internal refactoring
  • Minor bug fixes

Step 4: Search Current Codebase

For each critical/important change, search the codebase:

  1. Use Grep to find usages of:

    • Deprecated classes/methods
    • Changed API signatures
    • Affected dependencies
  2. Focus on these directories:

    • spring-data-jdbc-plus-support/
    • spring-data-jdbc-plus-sql/
    • spring-data-jdbc-plus-repository/
    • spring-boot-autoconfigure-data-jdbc-plus/

Step 5: Generate Report

Create a structured report with:

## Spring Data Relational {old} → {new} Upgrade Analysis

### Summary
- Total commits: X
- Files changed: Y
- Critical changes: Z

### Critical Changes Requiring Action

#### 1. [Change Category - e.g., API Deprecation]
**Upstream Change**: Description of what changed in spring-data-relational
**Impact**: Files in our codebase that are affected
**Action Required**: What needs to be done

[List specific files with line numbers if found]

### Important Changes to Review

[Same format as above]

### Dependency Updates

[List dependency version changes]

### Low Priority / Informational

[Brief list of other changes]

### Next Steps

1. [ ] Review critical changes
2. [ ] Update affected code
3. [ ] Update gradle.properties if needed
4. [ ] Run tests
5. [ ] Update documentation

Step 6: Provide Actionable Next Steps

  • Create TODO items for each required change
  • Suggest specific code modifications
  • Highlight test cases that should be added/updated

Examples

User: "Sync data-relational changes from 3.5.5 to 3.5.6" Skill:

  1. Fetches https://github.com/spring-projects/spring-data-relational/compare/3.5.5...3.5.6
  2. Identifies: API deprecations, dependency upgrades
  3. Searches codebase for affected code
  4. Generates report with action items

User: "What needs to be updated for spring-data-relational 3.5.6?" Skill:

  1. Checks current version in gradle.properties
  2. Compares with 3.5.6
  3. Provides analysis and action items

Important Notes

  • Always use TodoWrite to track the analysis tasks
  • Focus on changes that affect the core modules (support, sql, repository)
  • Consider backward compatibility when suggesting changes
  • Highlight security-related changes with high priority
  • Note any changes to transitive dependencies that might affect our users

Related Files

  • gradle.properties - Contains springDataBomVersion
  • buildSrc/src/main/groovy/spring.jdbc.plus.spring-bom-conventions.gradle - BOM configuration
  • spring-data-jdbc-plus-support/ - Core support module
  • spring-data-jdbc-plus-sql/ - SQL module
  • spring-data-jdbc-plus-repository/ - Repository module

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318399

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

340397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

452339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.