pr-draftlisted

# Draft a pull request Turn the current branch into a ready-to-paste PR title and body, grounded in the real commits and diff. Draft only: it does not create the PR. ## Step 1: Context and changes (one call) ```bash bash <skill-base-dir>/assets/pr_context.sh [base-ref] ``` Prints the branch, the issue key taken from the branch name, the resolved base, the commit list, the changed-file stat, and how many non-test files changed. Pass a base only when the user names one (`--tc` is a body-template flag, not a base). It resolves the base from the remote's own default branch, so a `develop`-based CUBRID repo works as well as a `main`-based one. If it reports no key, ask the user for it; if it cannot find a base, ask. Then read the key hunks of the diff (`git diff <base>...HEAD -- <path>`) where you need detail. Draft from what actually changed, not from memory. ## Step 2: Title `[XXX-0000] <summary>` - `[XXX-0000]` is the key from Step 1 (e.g. `[HHH-20527]`, `[CBRD-1234]`). - `<summary>` is concise **English** using easy words anyone can understand, one line, no trailing period. ## Step 3: Body (Korean, three sections) There are two body templates, and the default one is the default. - **Default**: use it unless told otherwise. - **TC template**: for **CMT (cubrid-migration) unit-test PRs only**. Select it only when the user passes `--tc` or says so explicitly ("TC PR", "단위 테스트 PR"). **Never switch to it just because the diff is test-only**: on another repo's test PR it