iamp5/springboot-copilot
Java/Spring rules, clean/hexagonal architecture guidance, COBOL migration and repair, and Maven verification
Design and review hexagonal or clean-architecture Java 25 / Spring Boot 4 modules - dependency direction, ports and adapters, use-case wiring, aggregates, value objects, Notification validation, sealed lifecycle states, domain events and outbox, transactions at the edge, SOLID decisions, strategy/observer/mediator patterns, scoped values, flexible constructors, Spring 7 resilience and HTTP service clients, and role-level tests. Use when a module declares architecture roles or its documents describe domain/application/infrastructure (or ports/adapters) layers.
Migrate mainframe COBOL business capabilities to Java 25 and Spring Boot APIs, or audit and repair previously migrated Java for JABOL patterns. Use for copybooks, working-storage state, paragraph-shaped services, decimal arithmetic, CICS/Db2 transactions, batch restart, API contracts, and legacy equivalence evidence.
Resolve Java 25 and Spring Boot 4 API changes when editing dependencies, JSON mapping, Spring tests, security configuration, HTTP clients, nullability, or concurrency code. Use for migrations and to avoid obsolete examples in new code.
Verify Java and Spring changes with existing Maven, tests, ArchUnit, lint, build, and optional SonarQube checks. Use before declaring completion, after failures, or when reviewing whether evidence covers the current code.
Write or review Java and Spring code using records, var, streams, functional interfaces, sealed types, exhaustive switches, domain validators, modern APIs, collection ownership, concurrency, transactions, persistence, tests, and existing architecture. Apply concrete rules with version bounds and justified exceptions.