What problem does it solve? Writing correct Neo4j client code in Java or Kotlin requires navigating driver lifecycle rules, transaction APIs, result consumption semantics, and error handling pitfalls that commonly cause bugs like ResultConsumedException, session leaks, and lost commits. ## Core Features & Use Cases - Driver Setup & Lifecycle: Maven/Gradle dependency configuration, single-driver-per-application pattern, URI scheme selection, and verifyConnectivity fail-fast checks. - Transaction APIs: Guidance on choosing between executableQuery, executeRead/executeWrite managed transactions, explicit transactions, async CompletableFuture, and reactive RxSession patterns. - Error Handling & Safety: Rules for consuming Result inside callbacks, null-safe value extraction, commit uncertainty, rollback safety, and UNWIND batch write parameter constraints. - Use Case: A developer building a Spring Boot service backed by Neo4j Aura uses this Skill to set up the driver, implement retry-safe writes with MERGE, and avoid returning un-consumed Result objects from transaction callbacks. ## Quick Start Ask the assistant to write a Java method that connects to Neo4j Aura and runs a parameterized read query using executableQuery with the database name specified.
