ha_repl-create

Create CUBRID CTP SQL testcases with --test/--check markers for HA replication.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly produce well-formed HA replication CUBRID CTP SQL testcases that follow CTP conventions, enforce commit/check discipline, and ensure master-to-slave consistency checks for new bug fixes or feature tests.

Core Features & Use Cases

  • Generates .sql test files annotated with --test: and --check: markers to drive master-only actions and cross-node verification.
  • Enforces one-statement-per-line rules, requires --test: COMMIT; after DML batches, and recommends deterministic ORDER BY in checks and explicit primary keys.
  • Use cases: drafting a new ha_repl testcase for a CBRD issue, creating DDL/DDL+data replication scenarios, and producing cleanup-safe, re-runnable tests that fit CTP directory conventions.

Quick Start

Create a draft ha_repl testcase for CBRD-12345 including header, setup, 3–6 check points, commit discipline, and cleanup.

Frequently Asked Questions about ha_repl-create

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

FAQPage Schema
How do I create HA replication testcases for CUBRID that follow CTP conventions?

To create HA replication testcases for CUBRID, generate SQL files with --test and --check markers that drive master actions and verify cross-node consistency. Ensure one-statement-per-line, explicit primary keys, and deterministic ORDER BY in checks.

What is the commit discipline required for CUBRID CTP replication test scripts?

CUBRID CTP replication test scripts require a --test: COMMIT; statement after DML batches to ensure changes are replicated from the master node to slave nodes before executing cross-node verification checks.

How do I structure a SQL test file for CUBRID master-to-slave replication verification?

Structure the SQL test file by separating master-only actions using --test: markers and cross-node verification using --check: markers, including a header, setup scripts, 3 to 6 check points, and cleanup steps for re-runnable tests.

Can I use CTP directory conventions to draft DDL and data replication scenarios for CBRD bug fixes?

Yes, you can draft DDL or DDL with data replication scenarios for CBRD bug fixes by following CTP directory conventions, applying per-statement markers, and referencing 3-node infrastructure configurations for cleanup-safe test execution.

Why do my CUBRID HA replication test checks fail to produce deterministic results?

HA replication test checks fail deterministically when SQL verification queries lack ORDER BY clauses or explicit primary keys. Enforce deterministic ORDER BY in checks and explicit primary keys during setup to guarantee consistent cross-node verification.

What are the limitations when writing ha_repl testcases for CUBRID features?

Limitations include strict formatting rules: one-statement-per-line is enforced, DML batches require explicit commit discipline, and tests must reference 3-node infrastructure configurations to properly verify master-to-slave replication consistency.