AI Agent Workflow Collection

Look up CUBRID Migration Toolkit (CMT) behavior in the official online manual at www.cubrid.org/cmtmanual: source database support (Oracle, MySQL, MariaDB, MSSQL, Informix, Tibero, and more), data type mapping, migration wizard steps, console/CLI mode, reports, and configuration. Use when migrating a database to CUBRID and you need to verify what CMT supports, how a source type maps to CUBRID, or how a CMT option or console command works. For CUBRID engine SQL/JDBC questions, use the cubrid-manual skill instead. Triggers on phrases like 'CMT', 'CUBRID Migration Toolkit', 'migrate X to CUBRID', 'CMT type mapping', 'how does CMT handle', 'CMT console mode'.

Look up CUBRID engine behavior in the official online manual: SQL syntax, built-in functions, data types, identifiers and reserved keywords, configuration parameters, and JDBC/driver APIs. Fetches the version-pinned manual at www.cubrid.org/manual. Use when you need to verify CUBRID SQL semantics, a function signature, a data type's range, whether a word is reserved, or a config parameter before writing dialect or JDBC code. For CUBRID Migration Toolkit (CMT) questions, use the cmt-manual skill instead. Triggers on phrases like 'how does X work in CUBRID', 'CUBRID syntax for', 'is X a reserved word in CUBRID', 'what functions does CUBRID have', 'check the CUBRID manual'.

Run the Hibernate ORM test suite against CUBRID and measure a dialect change's impact: total failures, +N recovered / −N regressed vs a baseline, and failures grouped by signature/family. Use when verifying a CUBRIDDialect change, an autoquote or capability-flag toggle, or any Hibernate-vs-CUBRID compatibility measurement. Pairs with the report skill (verify → numbers → 비교 분석 보고서). Triggers on phrases like 'dialect 검증', 'CUBRID 테스트 돌려', 'hibernate 스위트 실행', 'pass/fail 델타 측정', 'run the hibernate suite against CUBRID', 'measure dialect change'.

One-shot CUBRID dialect verification + report. Runs the hibernate-core test suite against one or ALL CUBRID versions, diffs pass/fail vs a baseline (a prior run's JSON, results dir, or .tgz), and ALWAYS produces a Korean Word (.docx) 비교 분석 report. Use when you want the full 'verify → measure → report' pipeline for a CUBRIDDialect change in one go, or to test across all CUBRID versions. Composes the hhh-dialect-verify and report skills. Triggers on phrases like 'dialect 검증하고 리포트까지', 'CUBRID 전체 버전 테스트 + 보고서', 'verify the dialect and write the report', 'run all CUBRID versions and report'.

Apply google-java-format (AOSP style, in place) to Java files: the changed files, the staged files, all files, or specific paths. It asks which google-java-format version to use (e.g. 1.7 or 1.32.0), resolves the jar (GJFJAR, then $GJFDIR if set, then a cache, else auto-downloads that version), and runs it. Use when you want to format Java code to the project style, before committing. Triggers on phrases like 'google-java-format 적용', '자바 코드 스타일 적용', '변경된 자바 포맷', 'format the java files', 'apply java formatting'.

One-shot CUBRID JDBC driver verification + report. Builds the CUBRID JDBC driver, runs the CTP JDBC test suite against CUBRID, diffs pass/fail vs a baseline (a prior run's JSON, CTP result dir, or test-jdbc.xml), classifies broken cases (VerifyError, conversion, broker/env, ...), and ALWAYS produces a Korean Word (.docx) 비교 분석 report. Use to verify a JDBC driver change or a Java-version/build-target change (e.g. v50 1.6 vs v52 1.8) end to end. Composes parsectp.py + the report skill. Triggers on phrases like 'JDBC 드라이버 검증', 'CTP 돌려', 'ctp jdbc 실행하고 리포트', 'verify the JDBC driver with CTP', 'build driver and run CTP'.

Draft a CUBRID JIRA issue (bug or task) with a concise English title and a Korean body under English section headers (Description as easy-to-read prose; the other sections in bullet style, 개조식). Use when you need to write up a CUBRID JIRA issue from the current work: a bug report (Description / Test Build / Repro / Expected / Actual / Additional Info) or a task/improvement (Description / Specification Changes / Implementation / Acceptance Criteria / Definition of Done). Produces a copy-paste draft only; it does not post to JIRA. It is the reverse of jira-fetch (which downloads an issue). Triggers on phrases like 'CUBRID JIRA 이슈 작성', 'jira 버그 리포트 초안', '이 작업 jira 이슈로 정리', 'draft a CUBRID jira issue', 'write a jira bug report'.

Download a JIRA issue to a local Markdown file to use as working context, via the Srltas/jira-to-md-downloader tool. Give it one or more issue keys (e.g. CBRD-1234, TOOLS-4888, APIS-1079, CUBRIDQA-123) and it fetches each issue's summary + description as .md, then loads it into the session so you can work against the ticket. Built for Jira Server/Data Center (REST API v2 + HTTP Basic auth); the target is CUBRID's Jira Server at jira.cubrid.org (any project: CBRD, TOOLS, APIS, CUBRIDQA, ...), and any other Jira Server instance works by setting JIRAURL. Atlassian Cloud (e.g. Hibernate HHH at hibernate.atlassian.net) is NOT supported as-is. It is the reverse of writing an issue up to JIRA. Triggers on phrases like 'CBRD-1234 내용 가져와', '이 이슈 md로 내려받아', 'jira 이슈 다운로드해서 참고', 'fetch jira issue as markdown'.