debug:spring-boot

To fix NoSuchBeanDefinitionException in Spring Boot, verify component scanning, check annotations, and confirm bean registrations. This skill provides a structured workflow to locate the missing bean, check its registration, and fix the configuration.

Diagnose Spring Boot startup errors by running the project with Actuator enabled and consulting /actuator/health and /actuator/mappings. This skill identifies port conflicts, context initialization errors, and bean initialization failures through targeted diagnostic steps.

The best way to resolve circular dependencies and Hibernate LazyInitializationException in Spring Boot is to identify and break cycles and manage N+1 queries. This skill applies structured error-pattern analysis to JPA and Hibernate problems.

Fix 403 errors, CSRF, and misbound properties in Spring Boot security configuration by applying targeted diagnostic steps. This skill helps resolve security configuration problems and environment binding issues through a structured debugging workflow.

Yes, this Spring Boot debugging workflow works for microservices deployments. It diagnoses DI failures, startup errors, and environment binding problems across typical Spring Boot deployments and microservices using Actuator endpoints.

You need Actuator endpoints to debug Spring Boot applications because they expose operational data like /actuator/health and /actuator/mappings. This skill leverages these endpoints to diagnose runtime issues, context initialization errors, and bean failures.