What problem does it solve?
When writing or reviewing BK-CI Spring Boot backend code, developers often lack a consistent reference for framework-level decisions such as configuration management, bean assembly, transaction boundaries, exception handling, and monitoring, leading to scattered practices and unstable services.
Core Features & Use Cases
- Configuration and Bean Assembly Guidance: Covers multi-environment configuration separation, type-safe binding, constructor injection, conditional assembly with @ConditionalOn*, and lifecycle boundary management.
- Data Access, Transactions, and Exceptions: Provides rules for repository design, transaction propagation, read-only queries, layered exception handling, and unified global error responses.
- Observability, Testing, and Quality: Defines expectations for Actuator endpoints, business metrics, structured logging, and layered testing strategies.
- Use Case: When refactoring a BK-CI microservice that mixes field injection, unclear transaction boundaries, and inconsistent exception responses, use this Skill to audit the code against framework best practices and produce a concrete improvement plan.
Quick Start
Review my Spring Boot service configuration and transaction handling against BK-CI backend conventions and point out violations.
