Skip to content

rrezartprebreza/spring-boot-skills / skills/spring-boot-3/null-safety

null-safety

Verified

Use when annotating nullability in Spring Boot 3 / Spring Framework 6 code, integrating Kotlin, or adding static nullability checks without assuming Spring Framework 7 JSpecify defaults.

Null Safety (Boot 3 / Framework 6)

Use the nullability model supported by the project. Spring Framework 6 commonly uses org.springframework.lang.Nullable, @NonNull, and package-level @NonNullApi. JSpecify can be introduced deliberately, but do not assume Framework 7 migration semantics in a Boot 3 module.

@NonNullApi
package com.example.orders;

import org.springframework.lang.NonNullApi;

Annotate genuine nullable results and parameters with @Nullable. Keep repository return types explicit, validate external input at boundaries, and use Kotlin compiler settings that match the annotations when Java and Kotlin are mixed. If the project standardizes JSpecify independently, apply it consistently at module boundaries and document the chosen checker.

Gotchas

  • Agent assumes Framework 7 JSpecify defaults - Boot 3 projects usually use Spring's legacy annotations.
  • Agent uses @NonNullApi without importing the package annotation - package metadata must compile and be checked in.
  • Agent marks every value @NonNull - establish a package default and annotate only nullable exceptions.
  • Agent treats annotations as runtime validation - use Bean Validation or explicit checks for input validation.
  • Agent changes a repository's nullable contract without updating callers - preserve Optional, nullable, and empty collection semantics.
  • Agent mixes JSpecify and Spring annotations without a migration plan - choose one module boundary policy.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall