CUBRID PR Creator

Create GitHub pull requests for the CUBRID project following team conventions.

Non-Negotiable Output Contracts

• The PR body always uses exactly these ## sections, in this order: ## Purpose, ## Implementation, ## Remarks.
• Keep ## headers in English and body prose in plain Korean.
• Put the JIRA issue URL at the very top, before ## Purpose.
• Keep the whole PR body to one screen, roughly 25-35 lines.
• Put deep technical detail in the separate markdown doc, not in the PR body.
• When the change has a clear before/after contrast, state AS-IS and TO-BE explicitly inside ## Purpose in both the PR body and detailed doc. Do not add new top-level sections for them.
• Never include local absolute paths, file:// URLs, or machine-specific workspace paths in PR material. Use repo-relative paths or public GitHub/JIRA URLs.
• Never include project shortcut commands beginning with the just task runner in PR material. Replace them with the actual public verification command, or describe the verification outcome in words.
• Run the bundled material checker before showing the body draft, before committing the doc repo, and before creating the PR.

Arguments

Pass optional arguments to customize: