
from skills13
Guided, modular migration of Spring Boot apps to Quarkus with gate-driven checks, safe edits, and a documented migration report.
This skill guides an agent through migrating a Spring Boot application to Quarkus. It provides a modular, gate-driven workflow (build, code, frontend, testing, cleanup) with explicit rules: never delete untranslatable code, always run builds and tests between phases, and document every decision. The skill includes reference maps for dependency, annotation, and configuration migration.
Use when a user asks to port or migrate a Spring Boot project to Quarkus, or mentions phrases like 'spring to quarkus', 'quarkus migration', or specific Spring artifacts (pom.xml, build.gradle, @SpringBootApplication, Thymeleaf). The skill is suitable for codebases where the agent can inspect build files and source to evaluate gate checks.
Suitable for developer-focused agents with code access (Codex/Copilot-style agents, OpenAI code models, or other code-aware assistants). The skill assumes availability of shell/build tooling for Maven/Gradle and git when branch workflows are chosen.
Comprehensive Spring Boot to Quarkus migration guide with gate-driven modular execution, decision tables, reference mappings, and a structured migration report template. No executable scripts — purely instruction-based. Well-organized with clear phases, verification steps, and self-reflection. Officially maintained by the Quarkus community.
No scripts present — static analysis only. Skill is a well-structured migration guide with excellent gate-driven architecture. The gate check system (PASS/SKIP/ALWAYS) is a good pattern for conditional module execution. Self-reflection step and migration report template add real value. The 'Critical Rules' section shows mature design thinking (never delete unmigrated code, don't break the build).