configuration-migration

Migrate configuration files, properties, and environment settings to target framework formats.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill configuration-migration-vanduc2514
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: configuration-migration
Source: https://github.com/vanduc2514/hackathon-lablab-ibm-bob/tree/main/.bob/skills/configuration-migration
Command: npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill configuration-migration-vanduc2514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating applications between frameworks or versions requires manually rewriting dozens of configuration files, property mappings, and environment settings, which is error-prone and often leaves deprecated or broken settings behind. ## Core Features & Use Cases - Property Mapping and Transformation: Converts configuration files between formats (properties, YAML, XML, JSON) with source-to-target property mappings, such as Quarkus to Spring Boot. - Environment-Specific Migration: Updates dev, test, and prod configurations while preserving environment parity and externalizing secrets. - Build and Security Config Updates: Migrates Maven/Gradle build settings, Spring Security configurations, and Dockerfiles to target platform conventions. - Use Case: When upgrading from Spring Boot 2.7 to 3.2, use this Skill to update application.yml properties, rewrite the SecurityConfig to the SecurityFilterChain pattern, bump the Java version in pom.xml, and produce an execution_configuration_changes.md report. ## Quick Start Migrate all configuration files in this project from Quarkus to Spring Boot format and document the property mappings and validation results.

Frequently Asked Questions about configuration-migration

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

FAQPage Schema
How do I migrate Quarkus configuration to Spring Boot?▼

Map Quarkus properties like quarkus.datasource.* to spring.datasource.*, quarkus.http.port to server.port, and quarkus.log.* to logging.*. Convert application.properties to application.yml and move concerns like CORS into Java configuration classes.

How to update Spring Security config from Spring Boot 2.7 to 3.2?▼

Replace the deprecated WebSecurityConfigurerAdapter with a SecurityFilterChain bean. Use authorizeHttpRequests with requestMatchers instead of authorizeRequests with antMatchers, and configure OAuth2 resource server with lambda-style DSL.

Does this handle environment-specific configuration files?▼

Yes, it migrates dev, test, and prod configurations while keeping their structure consistent. Production configs are updated to use environment variables for secrets, and logging or schema settings are adjusted per environment.

What happens to deprecated properties during migration?▼

Deprecated properties are identified and removed or replaced during migration. For example, Hibernate 6 in Spring Boot 3.2 no longer needs hibernate.jdbc.lob.non_contextual_creation, so it is dropped and noted in the migration report.

How is the migrated configuration validated?▼

Validation includes YAML syntax checks, confirming all required properties are present, verifying no deprecated properties remain, and testing that the application loads configurations successfully in each environment.