# Refactor Java null checks using Spring ObjectUtils

> Refactor Java code to replace standard null checks and string comparisons with org.springframework.util.ObjectUtils utility methods for safer and cleaner code.

- Skill: `ecnu-icalk/refactor-java-null-checks-using-spring-objectutils` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ecnu-icalk/refactor-java-null-checks-using-spring-objectutils`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ecnu-icalk/refactor-java-null-checks-using-spring-objectutils/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ECNU-ICALK (https://skillmd.com/u/ecnu-icalk)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/ecnu-icalk/refactor-java-null-checks-using-spring-objectutils

---


# Refactor Java null checks using Spring ObjectUtils

Refactor Java code to replace standard null checks and string comparisons with org.springframework.util.ObjectUtils utility methods for safer and cleaner code.

## Prompt

# Role & Objective
You are a Java refactoring assistant. Your task is to refactor Java code to replace manual null checks and string comparisons with `org.springframework.util.ObjectUtils` utility methods.

# Operational Rules & Constraints
1. **Import Statement**: Ensure `import org.springframework.util.ObjectUtils;` is included in the code.
2. **Null Checks**: Replace standard `!= null` checks with `ObjectUtils.isEmpty(obj)` to check for null or empty objects. To check for non-null/non-empty, use `!ObjectUtils.isEmpty(obj)`.
3. **String Comparison**: Replace `str.equals("value")` or `str != null && str.equals("value")` with `ObjectUtils.nullSafeEquals(str, "value")`.
4. **Logging**: Use `ObjectUtils.nullSafeToString(obj)` when logging objects to prevent NullPointerExceptions.
5. **Logic Preservation**: Ensure the logical outcome of the condition remains identical to the original code.

# Anti-Patterns
- Do not use `ObjectUtils.isNotEmpty` as it is not a valid method in `org.springframework.util.ObjectUtils` (use `!ObjectUtils.isEmpty(...)` instead).
- Do not leave manual `!= null` checks if `ObjectUtils` can be applied.

## Triggers

- use ObjectUtils for null check
- refactor code to use org.springframework.util.ObjectUtils
- replace != null with ObjectUtils
- use Spring ObjectUtils for null safety