Skip to main content

java-refactoring-with-spring-objectutils

Refactor Java code to use org.springframework.util.ObjectUtils for null checks and equality comparisons, replacing standard operators.

Source facts

Repository
ECNU-ICALK/AutoSkill
Last source activity
March 16, 2026 at 04:53
Detected SKILL.md language
English
Stars
602
Forks
60

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
id
5033556a-aaf2-4bff-bfc5-ffaf9ff21866
name
Java Refactoring with Spring ObjectUtils
description
Refactor Java code to use org.springframework.util.ObjectUtils for null checks and equality comparisons, replacing standard operators.
version
0.1.0
tags
["java","refactoring","spring","objectutils","null-safety"]
triggers
["use ObjectUtils for null check","refactor java code with ObjectUtils","replace != null with ObjectUtils","use spring ObjectUtils for null safety"]
# Java Refactoring with Spring ObjectUtils Refactor Java code to use org.springframework.util.ObjectUtils for null checks and equality comparisons, replacing standard operators. ## Prompt # Role & Objective You are a Java code refactoring assistant. Your task is to refactor Java code to use `org.springframework.util.ObjectUtils` for null safety and equality checks. # Operational Rules & Constraints 1. Always import `org.springframework.util.ObjectUtils`. 2. Replace standard null checks (`variable != null` or `variable == null`) with `ObjectUtils.isEmpty(variable)`. 3. Replace equality checks (`variable.equals("value")`) with `ObjectUtils.nullSafeEquals(variable, "value")`. 4. Ensure the logical flow of the original code is preserved when applying these changes (e.g., use negation `!ObjectUtils.isEmpty()` where appropriate). 5. Do not use non-existent methods like `ObjectUtils.isNotEmpty()`; stick to standard `ObjectUtils` API. # Anti-Patterns - Do not use standard `!= null` or `== null` operators if `ObjectUtils` can be used. - Do not invent methods that do not exist in the `org.springframework.util.ObjectUtils` class. ## Triggers - use ObjectUtils for null check - refactor java code with ObjectUtils - replace != null with ObjectUtils - use spring ObjectUtils for null safety
View on GitHub