Provides practical rules, recipes, and patterns for handling NullAway static analysis warnings in Java code. It explains when to use NullUtil.assumeNonNull(), when to assert != null, how to handle suppliers and generics, and migration vs new-code practices so teams can make null-safety changes with minimal regressions.
Use this skill when you're migrating existing Java code to @NullMarked, when you need to resolve NullAway warnings, or when writing new code that must follow Chromium null-safety conventions. Helpful during code review, refactoring, and constructing supplier-based APIs.
Compatible with developer/helpdesk/code-assistant agents that can present code snippets and guidance (e.g., Copilot-style coding assistants, Claude Code, or LLM-based code review helpers).
This skill has not been reviewed by our automated audit pipeline yet.
