spring-boot-knowledge-patch

Provides Spring Boot 3.4-4.0 breaking-change migration guidance for AI-generated code and configurations.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill spring-boot-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spring-boot-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/spring-boot-knowledge-patch/skills/spring-boot-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill spring-boot-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents AI-generated or human-edited Spring Boot code from using outdated APIs, incorrect starters, and deprecated configuration by providing concise, verified migration guidance and reference notes for versions 3.4–4.0 and Spring Framework 7.x.

Core Features & Use Cases

  • Starter and dependency renames: maps old spring-boot starters and libraries to the new modular starter names and classic/test fallbacks for gradual migration.
  • Jackson 3 migration: explains renamed classes and property keys and offers compatibility guidance and temporary compatibility flags.
  • HTTP clients, testing, and security: documents HttpExchange/RestClient usage, RestTestClient, PathPatternRequestMatcher, DSL changes, and security migration notes.
  • Spring AI and framework updates: includes Spring AI 1.0 examples (ChatClient, @Tool, VectorStore) and Spring Framework 7 changes like @Retryable in core and BeanRegistrar.
  • Use Case: migrate a codebase and CI tests from Spring Boot 3.x to 4.0 while ensuring configuration, JSON mapping, and security rules remain functional.

Quick Start

Load the spring-boot-knowledge-patch before generating or updating Spring Boot code so the model applies starter renames, Jackson 3 mappings, and breaking-change recommendations.

Frequently Asked Questions about spring-boot-knowledge-patch

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

FAQPage Schema
How do I migrate Spring Boot starters to the new modular names for version 4.0?

To migrate Spring Boot starters, you must map old spring-boot starters to the new modular starter names, utilizing classic and test fallbacks for gradual migration. This ensures dependency configurations remain functional and compile-ready during the Spring Boot 4.0 upgrade.

What changed in Jackson 3 migration for Spring Boot and how do I update property keys?

Jackson 3 migration involves updating renamed classes and property keys in your Spring Boot JSON mapping. You can apply provided compatibility guidance and temporary compatibility flags to transition configurations securely without breaking existing API contracts.

How do I update Spring Security DSL and PathPatternRequestMatcher for Spring Boot 4?

Updating Spring Security DSL involves applying documented migration notes for PathPatternRequestMatcher and DSL changes. This ensures your security rules remain functional and secure when upgrading codebases to Spring Framework 7.x and Spring Boot 4.0.

Does Spring AI 1.0 work with Spring Boot 4 and how do I use ChatClient and @Tool?

Spring AI 1.0 works with Spring Boot 4 by using updated ChatClient, @Tool, and VectorStore APIs. Applying the provided reference snippets ensures your AI integrations compile correctly and leverage the latest Spring Framework 7 capabilities.

How do I use HttpExchange and RestClient in Spring Framework 7 code generation?

Using HttpExchange and RestClient in Spring Framework 7 involves applying documented usage examples and replacement APIs. This updates HTTP service clients to reflect post-training breaking changes, resulting in compile-ready and secure network communication code.

When do I need a knowledge patch for Spring Boot migration?

You need a knowledge patch for Spring Boot migration when AI-generated code uses outdated APIs, incorrect starters, or deprecated configuration. Applying verified migration guidance for versions 3.4 to 4.0 prevents compilation errors and security misconfigurations.