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
npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a claude-codeWhat 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
SQLExceptionto domain errors - stream large
ResultSetvalues 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
ResultSetread to usesetFetchSizeand 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-code2Manually: put the files in place
~/.claude/skills/511-frameworks-micronaut-jdbc/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/511-frameworks-micronaut-jdbc/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a codex2Manually: put the files in place
.agents/skills/511-frameworks-micronaut-jdbc/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a cursor2Manually: put the files in place
.cursor/skills/511-frameworks-micronaut-jdbc/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/511-frameworks-micronaut-jdbc2Manually: put the files in place
.github/skills/511-frameworks-micronaut-jdbc/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/511-frameworks-micronaut-jdbcManually: put the files in place
.devin/skills/511-frameworks-micronaut-jdbc/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 511-frameworks-micronaut-jdbc -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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