my-cubrid-skills

Create CUBRID test cases (unit/SQL/shell) for a given feature or bug fix. Use when the user asks to create tests, write test cases, or mentions testing a CBRD ticket.

Iteratively implement CUBRID C/C++ code changes by looping a writer subagent against a relentless CUBRID PR-style reviewer subagent, with a build gate every round, until the reviewer explicitly approves or a round cap is hit. Accepts a JIRA issue, a GitHub PR URL, a spec path, or an inline spec - refuses to start without one. Trigger on phrases like 'implement and grill', 'grill the implementation', 'CUBRID grill-and-revise', 'implement CBRD-XXXXX with grill', 'implement and adversarially review', or 'grill until it compiles and passes review'.

Create and run CUBRID .ctl isolation tests for MVCC/concurrency scenarios. Use when the user asks to test isolation, concurrency, MVCC, locking, or multi-session behavior for a CUBRID feature.

Write a CUBRID JIRA issue report in Korean with English section headers (##). Top of issue is an Issue Triage block — 목적 (필수) + 이유 (필수, 현재 동작·한계와 그 영향 두 축을 모두 포함, 가능하면 AS-IS/TO-BE 대비 명시) + 방안 (합의된 스펙은 구체적으로, 미결정은 TBD) — written in whatever format reads best (short prose, mini-tables, ASCII call-flow diagrams, callouts — NOT forced dot-lists), followed by an explicitly separated AI-Generated Context block. Favors diagrams and comparison tables for call flows and option trade-offs. Writes structured markdown to /home/vimkim/gh/my-cubrid-jira/issues/. Use when the user wants to write up a JIRA issue, document a bug finding, or create a feature/task report for CUBRID.

Look up CUBRID JIRA issue context. Use when a CBRD-XXXXX ticket is mentioned or when the user asks about a JIRA issue.

Open a GitHub pull request for the CUBRID project with a [CBRD-XXXXX] title, Korean PR body, linked detailed doc, explicit AS-IS/TO-BE contrast when the change supports it, and pre-publish material checks. Use when the user wants to create, draft, push, or publish a CUBRID PR, including requests like "create pr", "make pr", "PR 만들어", "PR 올려", or "풀리퀘".

Review a CUBRID pull request from a CUBRID Git worktree whose current HEAD exactly matches the supplied PR number or URL, using the host CLI's native review engine and a local report. Uses Claude Code's built-in /code-review workflow or Codex CLI's built-in /review workflow, then applies CUBRID-specific checks. Use when the user requests review of the CUBRID PR currently checked out in the working directory.

Generate a polished, single-file HTML project schedule — either a daily Excel-like calendar grid or a Gantt timeline (or both) — from a set of work items, dates, and milestones. Use this whenever the user wants to visualize, lay out, or "예쁘게 뽑아줘" a project plan, merge/release schedule, roadmap, sprint, or 일정표 as HTML; whenever they ask for a Gantt chart, timeline, calendar view, or day-by-day plan; or whenever a planning/estimation discussion produces issues + durations + a target date that would be clearer as a visual. Trigger even if the user doesn't say "HTML" — if they're organizing a schedule to send to a manager or team, offer this. Especially fits CUBRID merge/milestone planning (e.g., feat branch → develop) with JIRA issue numbers, holidays, and review-gated timelines.

Analyze CircleCI/CI shell test failures for CUBRID PRs. Reads failed TC list, fetches CI results, reads test scripts and answer files, categorizes failures by root cause, and generates a structured report. Use when CI tests fail and the user wants to understand why.

Trigger CUBRID CI tests on a GitHub PR by posting a `/run` chatops comment — `/run sql medium` launches the SQL and medium suites, `/run all` launches sql, medium, and shell. Use for one-shot CI triggering when working on a CUBRID PR: after pushing new commits, when checks never started, or before requesting review. For hands-off fix-until-green iteration use cubrid-loop-pr instead. Triggers on phrases like 'trigger ci', 'run ci on this pr', 'kick off ci tests', 'run sql medium', 'run all tests on the pr', 'rerun ci', 'post the /run comment', 'start ci for the pr'.

Auto-iterate on a CUBRID PR by looping fix -> commit -> push -> trigger CI -> wait, until both `test_sql` and `test_medium` checks pass or a 24-hour cap is hit. Use when the user wants hands-off iteration on a PR until CI is green and is willing to leave the session running. Triggers on phrases like 'loop pr', 'loop on pr', 'auto-fix until ci passes', 'keep fixing until tests pass', 'iterate until sql and medium pass', 'run pr loop'.

Shared helper scripts for CUBRID skill preflight checks, PR metadata validation, CUBRID source-tree detection, build preset validation, and canonical CUBRID remote detection. Use when updating or debugging CUBRID skills that source common shell helpers; this is primarily an implementation dependency for other CUBRID skills.

Load CUBRID OOS (Out-of-row Overflow Storage) project context from the local knowledge base. Use this skill whenever OOS is mentioned, when working on the feat/oos branch, when touching oos_file.cpp or OOS-related heap_file.c code, when CBRD-26517/26458/26516 or other OOS JIRA tickets come up, or when you need to understand the OOS architecture, record format, CRUD flows, or MVCC integration. Also trigger when you see OOS-related identifiers like OR_MVCC_FLAG_HAS_OOS, OR_VAR_BIT_OOS, FILE_OOS, oos_insert, oos_read, oos_delete, or heap_record_replace_oos_oids.

Fetch and analyze authenticated pages from CUBRID's internal QA portal at qahome.cubrid.org. Use when the user gives a qahome.cubrid.org/qaresult URL, asks to read or parse shell/SQL/medium/functional QA result pages, asks for NOK lists or core stacks from qahome, or describes a portal navigation path such as cubrid / Recent builds(72h) / 11.5.0.2268-2c66b9a. The portal requires login; unauthenticated WebFetch or curl usually returns only the login form. Also use when resolving build tree ids, showstat pages, showFuntionRes summaries, showFailResult details, viewShellTestResult pages, or qahome frame/tree navigation.

Create a new skill in the my-cubrid-skills collection. Use when the user wants to turn a workflow into a reusable skill, capture what they just did as a skill, or add a new skill to their CUBRID toolbox. Triggers on phrases like 'make this a skill', 'create a skill for this', 'save this as a skill', 'add a new skill to my-cubrid-skills'.

Run one CUBRID CTP shell test (or a narrow subtree) against the local build. Use when the user wants to debug, reproduce, or iterate on a specific shell test (or a small bucket of them) without running the full CI suite. For CTP shell tests only — not for unit tests (cubrid-build), SQL regression tests, or .ctl isolation tests (cubrid-isolation-test). Triggers on phrases like 'run one shell test', 'debug a shell test', 'just shell-debug', 'ctp shell single test', 'run shell test for bug_XXXX', 'run itrack_XXXXX', 'reproduce CBRD-XXXXX shell test', 'rerun a CI shell failure locally', 'reproduce a CTP shell failure locally', 'rerun shell_ci.conf for one test', or 'ctp.sh shell'.

Fetch every comment on a GitHub PR by querying all three GitHub REST endpoints (inline review comments, top-level review summaries, and PR-page discussion) and merging them into one chronological view. Use when the user asks to list all PR review comments, audit reviewer feedback, or check whether anything was missed — a single endpoint fetch silently drops top-level review bodies and conversation-tab comments. Triggers on phrases like 'list all pr comments', 'all comments on pr', 'fetch every review comment', 'audit pr feedback', 'why are some review comments missing', or 'show every reviewer comment'.

CUBRID build and test workflow using justfile. Use when building, compiling, or testing CUBRID source code in any CUBRID worktree or source directory.

Resolve replied Greptile bot review comments on a GitHub PR. Use when the user wants to close, resolve, or dismiss Greptile comments that already have replies, or when they mention cleaning up bot review threads on a PR. Triggers on phrases like 'close greptile comments', 'resolve bot comments', 'clean up greptile threads', or 'dismiss replied review comments'.

Search the CUBRID manual (RST docs in en/ and ko/) for SQL syntax, configuration parameters, API references, admin utilities, and any CUBRID documentation. Use when you need to look up CUBRID behavior, verify SQL semantics, or answer questions about CUBRID features.