sync-data-relational

Extract changes between two spring-data-relational versions and generate an upgrade action report.

292|33|Updated Jan 14, 2020
One-click install
npx skills add https://github.com/naver/spring-jdbc-plus --skill sync-data-relational
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-data-relational
Source: https://github.com/naver/spring-jdbc-plus/tree/main/.claude/skills/sync-data-relational
Command: npx skills add https://github.com/naver/spring-jdbc-plus --skill sync-data-relational

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps synchronize spring-data-relational version updates to the spring-jdbc-plus project, ensuring compatibility and reducing upgrade effort.

Core Features & Use Cases

  • Fetches Version Diff: Retrieves changes between two spring-data-relational versions from GitHub
  • Analyzes Changes: Categorizes changes into API changes, dependency upgrades, bug fixes, and documentation updates
  • Identifies Impact: Searches the current codebase for affected code
  • Provides Action Items: Lists specific files and changes needed

Quick Start

Step 1: Check gradle.properties to find current springDataBomVersion and infer the target spring-data-relational version. Step 2: Use the GitHub compare URL: https://github.com/spring-projects/spring-data-relational/compare/{old-version}...{new-version} Step 3: Analyze changes and categorize into critical and important changes. Step 4: Grep the codebase for usages of changed APIs and affected dependencies. Step 5: Generate a structured report with action items in the repository. Step 6: Create TodoWrite items to track the upgrade tasks.

Frequently Asked Questions about sync-data-relational

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify what changes when upgrading spring-data-relational versions?

Extract changes between versions by comparing GitHub repositories to categorize API changes, dependency upgrades, bug fixes, and documentation updates. This identifies which spring-data-jdbc-plus modules are affected and what code needs updating.

Can I automate syncing spring-data-relational upgrades across my project?

Yes. Analyze the diff between old and new versions, search your codebase for affected APIs and dependencies, then generate a structured action report mapping changes to specific files requiring updates.

What's the best way to handle spring-data-relational BOM version changes?

Check gradle.properties for the current springDataBomVersion, use GitHub compare URLs to fetch the version diff, categorize changes into critical and important buckets, then grep the codebase for usages and create tracked upgrade tasks.

How do I find which files in my codebase are affected by spring-data-relational API changes?

Map each change from the version diff to affected files by performing repository searches for usages of changed APIs and impacted dependencies in spring-data-jdbc-plus modules.

Does this work for upgrading spring-boot-autoconfigure-data-jdbc-plus and spring-data-jdbc-plus-repository?

Yes. This skill analyzes changes across all spring-jdbc-plus modules including spring-data-jdbc-plus-support, spring-data-jdbc-plus-sql, spring-data-jdbc-plus-repository, and spring-boot-autoconfigure-data-jdbc-plus.