CUBRID PR CI Loop

Iteratively fix a CUBRID PR until the CircleCI test_sql and test_medium checks both pass, or until a 24-hour wall-clock cap is reached. Each round delegates the actual code fixing to /cubrid-grill-and-implement and only handles the outer loop: commit, push, trigger CI, wait, parse results, and either stop or start the next round.

When to Use

• User wants hands-off iteration on a PR until CI is green and is OK leaving the session running for hours.
• User says "loop the PR", "keep fixing until CI passes", "auto-iterate on PR until sql/medium pass".
• User explicitly shares a PR URL plus an intent describing what the PR should achieve.

Do NOT trigger this for one-off fixes. The skill is expensive (multi-round grill + multiple CircleCI runs) and only makes sense when the user has explicitly accepted the long-running, multi-hour shape.

Arguments

• /cubrid-loop-pr <pr-url> <intent> — Loop on the given PR with the given intent (single-line description of what should ultimately work).
• /cubrid-loop-pr <pr-url> — Refuse and ask for an explicit intent string.
• /cubrid-loop-pr — Refuse and ask for both arguments.

<intent> should be a complete sentence. It is forwarded verbatim to /cubrid-grill-and-implement every round and is what the loop is ultimately optimizing for. Vague intents produce vague fixes.