java-framework-production-readiness

name	java-framework-production-readiness
description	Use this skill when statically reviewing a Spring Boot, Quarkus, or Micronaut service for production readiness — externalized configuration, health/readiness/liveness endpoint wiring, graceful shutdown, jakarta namespace correctness plus the framework's JDK floor, build-time DI/AOT reflection safety, profile/config validation, and dependency BOM alignment. Trigger when a user provides a build file (pom.xml/build.gradle), application.properties/application.yml (sanitized), or source annotations and asks whether a service is ready to ship, what a pre-production checklist should cover, or why a rolling deploy drops requests or a native build fails at runtime. Reads source and sanitized configuration only; it never builds, runs, invokes a JDK, opens a live connection, or asserts framework EOL dates from memory.
allowed-tools	Read Grep Glob
metadata	{"author":"github: Raishin","version":"0.1.0","updated":"2026-07-17","category":"architecture","lifecycle":"experimental"}

java-framework-production-readiness

Purpose

This skill statically assesses whether a Spring Boot, Quarkus, or Micronaut service is production-ready and issues a single ship / do-not-ship verdict. Readiness is framework-specific: the same conceptual checklist item (health endpoints, graceful shutdown, reflection safety) is implemented differently by each framework, and applying the wrong framework's pattern produces false confidence. The skill first identifies the exact framework and version in scope, then walks a seven-part checklist — externalized config, health/liveness/readiness wiring, graceful shutdown, jakarta namespace correctness paired with the JDK floor, build-time DI/AOT reflection safety, profile/config validation, and dependency BOM alignment — labeling every finding with its evidence basis and citing framework EOL/support facts only from verified reference data, never from memory.