ci-checklisted

# Triage a CUBRID PR's CI failure Decide what to do about a red PR: re-run it, update its base, or dig in. Built for submodule bump PRs on `CUBRID/cubrid`, but it works on any PR of that repo. **Analysis only**: it never re-runs CI and never pushes. ## Step 0: How CUBRID's CI is laid out (why this skill works the way it does) - The real tests run on **CircleCI** (`build`, `build_debug`, `test_medium`, `test_sql`, `test_shell`). GitHub Actions only carries lint and style checks (`code-style`, `cppcheck`, `license`, `pr-style`, ...). - CircleCI's v1.1 API is readable **without a token** for this public project, so failing tests and their output can be pulled directly. Re-running a job, however, needs a token, which is why this skill only reports. - **`develop` runs only `build` and `build_debug`.** There is no develop run of the test jobs, so there is no baseline saying "this test is already broken on develop". The skill uses **recent runs of the same job on other PRs** as a stand-in. That is an approximation: treat 공통 as strong evidence, not proof. ## Step 1: Run it ```bash python3 <skill-base-dir>/assets/ci_check.py [PR] ``` `PR` is a number or URL; with no argument it uses the current branch's PR. Needs `gh` (authenticated), `curl`, and `python3`. **A green PR costs nothing**: the script prints the check summary and stops. The 1-2 MB test payloads are downloaded only when a CircleCI test job actually failed, so this is also the right command for a plain "is CI ok?" qu