cci-runone

Execute and analyze a single CCI testcase with pass/fail reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill executes a single CUBRID CCI testcase on a local machine, determines pass or fail status, and synthesizes actionable diagnostics to reduce manual triage time.

Core Features & Use Cases

  • Locate CCI test cases inside the cubrid-testcases-private repository using test names or issue numbers and read test scripts and test.c before running.
  • Prepare the environment and install a provided CUBRID build, execute the test with timeout handling, capture outputs, and read result files to report pass or fail.
  • Perform structured failure analysis including compile errors, CCI runtime errors, server and broker logs inspection, core dump checks, and expected-vs-actual output comparison.

Quick Start

Request the skill to run a specific CCI test by providing the CUBRID build URL and the test path or name.

Frequently Asked Questions about cci-runone

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

FAQPage Schema
How do I run a single CCI testcase locally using a CUBRID build URL?

To run a single CCI testcase locally, provide a valid CUBRID build URL and the test path to the skill. It prepares the environment, installs the build, executes the test, and generates a pass or fail report with actionable diagnostics.

What do I need to diagnose CCI test failures on my local machine?

Diagnosing CCI test failures requires a local CTP installation, sourced CUBRID environment variables, a valid CUBRID build URL, and access to the cubrid-testcases-private repository to locate test scripts and perform structured failure analysis.

How does CCI failure analysis handle compile errors and core dumps?

CCI failure analysis inspects compile errors, CCI runtime errors, server and broker logs, and checks for core dumps. It compares expected versus actual outputs to synthesize actionable diagnostics and reduce manual triage time.

Can I execute CTP CCI test runs for one-off checks without a full suite?

Yes, you can execute one-off CTP CCI test runs by providing a specific test name or issue number. The skill locates the corresponding test case inside the cubrid-testcases-private repository, reads the scripts, and runs it individually with timeout handling.

Why does my single CCI test execution require access to the cubrid-testcases-private repository?

Access to the cubrid-testcases-private repository is required because the skill needs to locate the CCI test cases using test names or issue numbers, and read the test scripts and test.c files before executing and analyzing the run.

What's the best way to analyze CUBRID CCI runtime errors and server logs after a test run?

The best way to analyze CUBRID CCI runtime errors is using automated structured failure analysis, which inspects server and broker logs, checks for core dumps, and compares expected versus actual outputs to pinpoint the root cause.