511 frameworks micronaut jdbc

Skill jabrena/plinth/skills/511-frameworks-micronaut-jdbc

Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.

Install

npx -y skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.4 KB, as published. Nobody here has run it

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

Read reference and assess project context

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

Gather scope and decide target improvements

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

Apply framework-aligned changes

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

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.