jdbc-create

Generate JDBC JUnit 4 Java testcase templates for CUBRID CTP tests.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/tw-kang/skills --skill jdbc-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jdbc-create
Source: https://github.com/tw-kang/skills/tree/main/jdbc-create
Command: npx skills add https://github.com/tw-kang/skills --skill jdbc-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone work of writing new JDBC testcases for the CUBRID CTP by providing clear templates, naming conventions, and a self-review checklist so tests conform to CTP expectations.

Core Features & Use Cases

  • Generate templates for JUnit 4 Java test classes tailored to bug fixes (CBRD-####), feature specs, or general JDBC testcases.
  • Enforce conventions including package and class naming, method names containing "test", PropertiesUtil usage for connection parameters, DROP/CREATE table patterns, resource cleanup, and @Ignore usage for skipped tests.
  • Operational guidance including CTP installation detection, directory path conventions, example test structure, and a self-review checklist to validate produced code before commit.
  • Use Case: Quickly draft a JUnit test class for a CBRD bug, ensuring it follows CTP directory/package rules and contains safe setup/teardown and assertion patterns.

Quick Start

Generate a JDBC JUnit 4 test scaffold for CBRD-12345 that follows CTP naming, package, and cleanup conventions.

Frequently Asked Questions about jdbc-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a JUnit 4 JDBC test case template for a CUBRID bug fix?

You can scaffold a JUnit 4 JDBC test case by providing a bug identifier like CBRD-#### to generate a Java test class template that automatically follows CTP directory and package naming conventions.

What conventions must CUBRID CTP JDBC test cases follow?

CUBRID CTP JDBC test cases must follow conventions including package and class naming, method names containing "test", PropertiesUtil-based connection setup, DROP/CREATE table patterns, and resource cleanup in finally blocks.

Does this scaffolding process handle database connection setup and teardown automatically?

Yes, the scaffolding process handles connection setup and teardown by generating templates with PropertiesUtil-based connection parameters and resource cleanup in finally blocks for safe test execution.

Can I use this to create test scaffolds for general JDBC connection and ResultSet feature tests?

Yes, you can create test scaffolds for general JDBC connection, statement, and ResultSet feature tests, as well as specific CBRD bug fixes, tailored to standard CTP directory structures.

What is the best way to ensure my generated JDBC test code passes CTP review?

The best way to ensure generated JDBC test code passes CTP review is to apply the provided self-review checklist, validating JUnit assert usage, naming conventions, and @Ignore tags before committing.