Generate CUBRID CTP isolation testcase .ctl files from bug or feature descriptions.
npx skills add https://github.com/tw-kang/skills --skill isolation-create
Please help me install this Agent Skill. Skill: isolation-create Source: https://github.com/tw-kang/skills/tree/main/isolation-create Command: npx skills add https://github.com/tw-kang/skills --skill isolation-create
Creating well-formed CUBRID CTP isolation testcase files is repetitive and error-prone, and teams need consistent scaffolding, headers, synchronization, and cleanup to avoid flaky or non-runnable tests. This Skill provides a rule-driven template and checklist so authors can produce ready-to-run .ctl files that follow CTP conventions and directory naming standards.
Create an isolation testcase draft for CBRD-12345 that verifies read committed lock contention between two clients.
High-intent search queries and answers about installing and using this skill.
CUBRID CTP isolation testcases are generated by processing a bug or feature description into .ctl files. The output includes properly formatted headers, NUM_CLIENTS setup, MC and Cx synchronization commands, lock timeout settings, and cleanup steps for concurrent clients.
An isolation test in CUBRID verifies database behavior with two or more concurrent clients under isolation levels like READ COMMITTED, REPEATABLE READ, and SERIALIZABLE. A .ctl file is needed to define MC and Cx commands, synchronization barriers, and cleanup steps for the CTP framework.
Structure a .ctl file by following CTP header and body conventions, setting NUM_CLIENTS, defining MC and Cx commands with synchronization barriers, configuring lock timeout and isolation levels, and adding explicit client quit and cleanup steps to prevent interleaving issues.
Yes, CUBRID CTP supports isolation level directories and sequential testcase numbering. Generated .ctl files enforce these directory naming standards, placing tests under appropriate isolation-level directories with correct sequential numbering and documentation for bug-fix or feature scenarios.
CUBRID isolation tests fail with interleaving when missing synchronization barriers between MC and Cx commands. Generated .ctl files prevent this by enforcing explicit lock timeout setup, isolation settings, synchronization barriers, and explicit client quit commands to ensure proper cleanup and sequential execution.
Yes, you can create isolation test variants for different concurrency scenarios in CUBRID. The generation process produces scenario variants with correct sequential numbering, proper documentation, and formatted .ctl files supporting common isolation level combinations like READ COMMITTED, REPEATABLE READ, and SERIALIZABLE.
tw-kangRun a single CTP isolation testcase (.ctl) and report pass/fail.
tw-kangExecute a named CUBRID shell testcase locally and report pass/fail results.
tw-kangExecute and analyze a single CCI testcase with pass/fail reports.
djimitExecute tests in isolation within the opencode-swarm ecosystem.
