sync-data-relational
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.zipInstalls 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
- Fetches Version Diff: Retrieves changes between two spring-data-relational versions from GitHub
- Analyzes Changes: Categorizes changes into:
- API changes (new methods, deprecated methods, signature changes)
- Dependency upgrades
- Bug fixes
- Documentation updates
- Identifies Impact: Searches the current codebase for affected code
- Provides Action Items: Lists specific files and changes needed
Instructions
Step 1: Determine Versions
- Check
gradle.propertiesto find currentspringDataBomVersion - 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
- 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:
-
Use Grep to find usages of:
- Deprecated classes/methods
- Changed API signatures
- Affected dependencies
-
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:
- Fetches https://github.com/spring-projects/spring-data-relational/compare/3.5.5...3.5.6
- Identifies: API deprecations, dependency upgrades
- Searches codebase for affected code
- Generates report with action items
User: "What needs to be updated for spring-data-relational 3.5.6?" Skill:
- Checks current version in gradle.properties
- Compares with 3.5.6
- 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 springDataBomVersionbuildSrc/src/main/groovy/spring.jdbc.plus.spring-bom-conventions.gradle- BOM configurationspring-data-jdbc-plus-support/- Core support modulespring-data-jdbc-plus-sql/- SQL modulespring-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.
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.
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."
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.
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.
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.
Related MCP Servers
Browse all serversTrade crypto easily with CCXT Crypto Trading bot. Monitor, analyze, and execute trades across 100+ exchanges with this c
Unlock Instagram insights to boost advertising and marketing services. Analyze interactions for better IG engagement and
Automate your figma to code workflow. Convert Figma designs to HTML, extract SVGs, analyze color, and generate CSS with
TON Blockchain Analyzer tracks wallet addresses, analyzes transactions, and uncovers trading patterns for smarter crypto
Enhance Java code with Aibolit Java Code Analyzer. Identify design, maintainability, and architectural issues beyond sur
Volume Wall Detector analyzes trading data to spot volume walls and key price levels for better market insights and pote
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.