create-prlisted

# Create PR ## Workflow ### 1. Gather context ```bash ~/.claude/skills/create-pr/scripts/gather_pr_context.sh [BASE_BRANCH] ``` Prints repo type (CK or generic), current branch, base branch, commits ahead, diff stat, and a warning with `git status --short` if uncommitted changes exist. Read the "Repo type" line first — it tells you whether to follow the CK-specific conventions below. Base branch defaults to `develop` in a detected CK repo, otherwise the repo's default branch (`origin/HEAD`, falling back to `main`). If uncommitted changes exist, warn the user before proceeding. ### 2. Collect PR details Ask the user (skip fields they've already provided): - **Title**: suggest one from the commit history. In a CK repo, prefix with `[CK]`. - **Motivation**: why this change exists, linked PRs/issues. - **Technical Details**: key implementation choices (draft bullet points from the diff if the user wants help). In a non-CK repo, also check for a repo PR template (`.github/PULL_REQUEST_TEMPLATE.md` or `.github/PULL_REQUEST_TEMPLATE/`) and follow it instead of the generic template in step 4 if one exists. ### 3. Collect test evidence Ask if the user wants to run tests now or paste existing output. - **CK repo**: delegate test runs to a sub-agent. Run CK GPU tests with `ckRun` (`REPO=$(git rev-parse --show-toplevel) ckRun --arch <gfx> <cmd>`), which dispatches to a GPU (srun/docker/direct auto-detected); for many runs start a holder once with `ckHold --arch <gfx>`