ha-shell-create

Generate CUBRID CTP HA shell test scripts for replication scenarios.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill produces well-formed CUBRID CTP HA shell testcase drafts so engineers no longer have to manually assemble HA setup, replication checks, and cleanup boilerplate for HA scenarios.

Core Features & Use Cases

  • Structured HA lifecycle: Ensures scripts use bash, source init.sh and make_ha.sh, call setup_ha_environment, and always call revert_ha_environment before finish.
  • Replication & failover patterns: Generates patterns for DML replication verification, failover promotion checks, and configuration-change tests using run_on_slave and wait_for_slave helpers.
  • CTP conventions & placement: Adheres to CTP naming, directory placement under cubrid-testcases-private/HA/shell, uses dbname=hatestdb, and forbids hardcoded hosts or absolute paths.

Quick Start

Create a draft HA shell testcase that sets up hatestdb, verifies replication with wait_for_slave, and includes proper cleanup with revert_ha_environment.

Frequently Asked Questions about ha-shell-create

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

FAQPage Schema
How do I generate CUBRID HA shell test scripts for replication testing?

To generate CUBRID HA shell test scripts, this Skill creates drafts that source init.sh and make_ha.sh, call setup_ha_environment, and enforce CTP conventions for replication testing. It ensures proper lifecycle management by inserting revert_ha_environment before script finish.

What is the standard structure for a CTP HA failover simulation testcase?

A standard CTP HA failover simulation testcase uses bash, sources init.sh and make_ha.sh, and calls setup_ha_environment. It verifies failover promotion using run_on_slave and wait_for_slave helpers, then cleans up with revert_ha_environment.

How do I verify DML replication in CUBRID HA without hardcoding hostnames?

To verify DML replication in CUBRID HA without hardcoding hostnames, use generated test patterns with run_on_slave and wait_for_slave helpers. The scripts enforce CTP conventions that prohibit absolute paths and hardcoded hosts, ensuring portable replication verification.

Can I use this to automate HA configuration change tests for CUBRID?

Yes, you can automate HA configuration change tests for CUBRID. The generated shell scripts adhere to CTP naming and directory placement under cubrid-testcases-private/HA/shell, using hatestdb to validate configuration changes with proper environment setup and cleanup.

Why does my CUBRID HA shell testcase fail during environment setup?

Your CUBRID HA shell testcase may fail if it lacks proper sourcing of init.sh and make_ha.sh, or misses setup_ha_environment calls. Hardcoded hostnames and absolute paths are prohibited by CTP conventions and will also cause failures.

What is the correct directory placement for CUBRID HA CTP shell testcases?

The correct directory placement for CUBRID HA CTP shell testcases is under cubrid-testcases-private/HA/shell. Scripts must follow CTP naming conventions, use dbname=hatestdb, and avoid hardcoded hosts or absolute paths to ensure proper execution.