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.

Quellinformationen

Repository
ECNU-ICALK/AutoSkill
Letzte Quellaktivität
16. März 2026 um 04:53
Erkannte Sprache von SKILL.md
Englisch
Sterne
602
Forks
60

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
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
Auf GitHub ansehen