Skip to main content
skill CX Codex

511-frameworks-micronaut-jdbc — Claude Code skill

511-frameworks-micronaut-jdbc — a skill for reviewing Micronaut JDBC code, covering SQL binding, transactions, pooled connections, batching, and database error mapping.

Apache-2.0 318 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a claude-code
Open on GitHub

What 511-frameworks-micronaut-jdbc does

This skill reviews programmatic JDBC in Micronaut around an injected javax.sql.DataSource, including the Hikari setup supplied by micronaut-jdbc-hikari. It checks PreparedStatement binding, row mapping into Java records, single-result queries with Optional<T>, and conversion of SQLException into domain exceptions. Large result sets are handled with setFetchSize; bulk inserts use addBatch and executeBatch.

It also examines @Transactional service boundaries, TransactionDefinition.Propagation, and self-invocation where this.method() bypasses the transactional collaborator. The workflow reads references/511-frameworks-micronaut-jdbc.md, inspects the project, applies the smallest suitable change, then verifies it. Run ./mvnw compile or mvn compile before editing. If compilation fails, the skill stops; after the changes, run ./mvnw clean verify or mvn clean verify.

What it helps with

  • review SQL parameter binding
  • define Micronaut transaction boundaries
  • map SQLException to domain errors
  • stream large ResultSet values safely
  • batch bulk insert operations

Example prompts for the agent

  • Review the Micronaut JDBC access and replace unsafe SQL construction with bound parameters.
  • Fix the self-invocation that bypasses @Transactional, then verify the service boundary.
  • Refactor the large ResultSet read to use setFetchSize and check the build.

How to install 511-frameworks-micronaut-jdbc

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a claude-code

2Manually: put the files in place

~/.claude/skills/511-frameworks-micronaut-jdbc/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/511-frameworks-micronaut-jdbc/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 511-frameworks-micronaut-jdbc

How do I install 511-frameworks-micronaut-jdbc in Claude Code?

Run npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a claude-code, then check ~/.claude/skills/511-frameworks-micronaut-jdbc/SKILL.md.

What does 511-frameworks-micronaut-jdbc do?

It applies Micronaut JDBC patterns for bound SQL, pooled DataSource usage, transaction handling, batch updates, streamed result sets, and domain-level database errors.

How does it handle large result sets?

The skill recommends setFetchSize so rows can be streamed instead of loading the full result set into memory.

Source text

SKILL.md · Apache-2.0
---
name: 511-frameworks-micronaut-jdbc
description: Use when you need programmatic JDBC in Micronaut — pooled DataSource, parameterized SQL, io.micronaut.transaction.annotation.Transactional, batching, and domain exception translation. This should trigger for requests such as Review JDBC or SQL data access in a Micronaut project; Improve transactions and parameter binding for Micronaut JDBC; Translate SQLException to domain exceptions or stream large result sets; Fix self-invocation bypassing @Transactional in Micronaut; Review Hikari or pooled datasource usage in Micronaut JDBC. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Micronaut JDBC — programmatic SQL

Apply programmatic JDBC patterns in Micronaut with safe SQL and clear transactions.

**What is covered in this Skill?**

- Injected javax.sql.DataSource (Hikari-backed with micronaut-jdbc-hikari) and try-with-resources for Connection / PreparedStatement
- PreparedStatement with bind parameters — never string concatenation
- Mapping ResultSet rows to Java records (dedicated mapRow method)
- Safe single-row queries with Optional<T>; never assume rs.next() succeeds
- SQLException translation to domain exceptions (catch-translate-rethrow)
- Streaming large result sets with setFetchSize to avoid OOM
- Batch updates with addBatch / executeBatch for bulk inserts
- @Transactional service boundaries and TransactionDefinition.Propagation (e.g. REQUIRES_NEW for independent commits)
- Self-invocation pitfall: call transactional collaborators through injected beans, not this.method()
- SQL text blocks for multi-line SQL (upserts, dialect-specific clauses)
- When to prefer Micronaut Data (`@512`) vs raw JDBC

**Scope:** Apply recommendations based on the reference rules and good/bad code examples.

## Constraints

Compile before JDBC refactors; verify after changes.

- **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change
- **PREREQUISITE**: Project must compile before applying JDBC improvements
- **SAFETY**: If compilation fails, stop immediately
- **BLOCKING CONDITION**: Compilation errors must be resolved by the user before proceeding
- **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements
- **BEFORE APPLYING**: Read the reference for detailed rules and examples

## When to use this skill

- Review JDBC or SQL data access in a Micronaut project
- Improve transactions and parameter binding for Micronaut JDBC
- Translate SQLException to domain exceptions or stream large result sets
- Fix self-invocation bypassing @Transactional in Micronaut
- Review Hikari or pooled datasource usage in Micronaut JDBC

## Workflow

1. **Read reference and assess project context**

Read `references/511-frameworks-micronaut-jdbc.md` and inspect the current project setup before proposing changes.

2. **Gather scope and decide target improvements**

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

3. **Apply framework-aligned changes**

Implement or refactor configuration/code following the reference patterns and project conventions.

4. **Run verification and report results**

Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.

## Reference

For detailed guidance, examples, and constraints, see [references/511-frameworks-micronaut-jdbc.md](references/511-frameworks-micronaut-jdbc.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Backend and APIs →

From the same set123

The whole set →
512-frameworks-micronaut-data 512-frameworks-micronaut-data — a skill for Micronaut Data work: entity mapping, repositories, transactions, pagination, projections and Testcontainers tests. CX Codex +1 322installs 502-frameworks-micronaut-rest 502-frameworks-micronaut-rest guides your coding agent in designing and reviewing Micronaut REST APIs. Enforces strict HTTP semantics and OpenAPI alignment. CX Codex +1 322installs 523-frameworks-micronaut-testing-acceptance-tests 523-frameworks-micronaut-testing-acceptance-tests turns maintainer-approved Gherkin scenario facts into working Micronaut acceptance tests over real HTTP, with Testcontainers and WireMock. CX Codex +1 321installs 702-technologies-wiremock 702-technologies-wiremock delivers framework-neutral WireMock guidance for HTTP stub design, dynamic ports, and stable test isolation. CX Codex +1 318installs 513-frameworks-micronaut-db-migrations-flyway The 513-frameworks-micronaut-db-migrations-flyway skill guides Flyway migration work in Micronaut, covering SQL files, datasource settings, migration order, tests, and schema-change safety. CX Codex +1 317installs 002-agents-inventory 002-agents-inventory — a skill to auto-generate a checklist with an embedded Java agent inventory. Produces INVENTORY-AGENTS-JAVA.md by strictly following a template, preserving exact structure and content. CX Codex +1 314installs 043-planning-github-issues 043-planning-github-issues guides GitHub CLI setup and keeps issue prose outside agent context, relying on repository-owned documents for requirements analysis. CX Codex +1 312installs 126-java-exception-handling 126-java-exception-handling is a Claude Code skill for Java exception handling. It activates on requests to review error types, resource cleanup, or failure propagation. CX Codex +1 307installs

Project sponsors

Companies that keep this analytics open