" --body-file <(printf "...")` - If PR already exists or `--fill` is required: `gh pr edit <number> --body "<body>"` - Use `gh pr view/diff` to inspect the PR state/diff. - Consider optional version bump labels (`version:bump-minor|version:bump-major`) based on change impact. Required labels: - `type/feature` - `type/fix` - `type/chore` - `type/skip-changelog` ## Step 6: CI check - Loop: `gh run list` → `gh run view <id>` → fix → push → repeat until green (usually 60–90s). - If CI returns qlty feedback, address it, then re-run. - Run `bin/ci --no-signoff` before pushing; after push, run `bin/ci`. ## PR Body Template (from `.github/PULL_REQUEST_TEMPLATE.md`) ``` ## Summary - ... ## Label Checklist **Required** — pick exactly one `type/` label: - [ ] `type/feature` — new functionality - [ ] `type/fix` — bug fix or correction - [ ] `type/chore` — maintenance, refactor, deps - [ ] `type/skip-changelog` — docs/CI, no user impact **Optional** — version bump (default: patch): - [ ] `version:bump-minor` — new feature (1.0 → 1.1) - [ ] `version:bump-major` — breaking change (1.0 → 2.0) ``` --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jandragsbaek) — claim your Tome and manage your conversions. <!-- tomevault:4.0:skill

# Create Pr > Create a fresh feature branch from main, rebase on latest main, and open a GitHub PR with a solid summary/testing notes. Use when asked to “start a branch,” “rebase from main,” “open a PR,” or “get a PR going.” Use when this capability is needed. - Skill: `tomevault-io/create-pr-24` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/create-pr-24` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/create-pr-24/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/create-pr-24 --- # Create PR ## Overview Fast, safe branch setup + rebase on `origin/main`, then open a PR with required labels and a detailed description. ## Workflow Decision Tree - Working tree dirty? Review `git status/diff` to confirm scope; ask before proceed if unrelated/unexpected. - User asked for new branch? Create from `origin/main`. - User asked for rebase? Rebase branch onto `origin/main`. - PR requested? Create via `gh pr create` and add required label. - Skill invoked: you have consent to switch branches and must generate a sensible branch name. - Check available skills; apply any that match the request. ## Step 1: Preflight - `git status -sb` - `git --no-pager diff --color=never` - If dirty: check for unrelated/unexpected changes; ask before proceed. - Skill invocation grants branch switch consent. - Branch naming: infer from scope + change type. Format: `/-`, lowercase, hyphens. - Examples: `chore/skills-pr-flow`, `docs/skills-docs-first`, `fix/ci-loop-q-lty`. ## Step 2: Sync main - `git fetch origin` - `git checkout main` - `git pull --ff-only` ## Step 3: Create or update branch New branch: - `git checkout -b origin/main` Existing branch: - `git checkout ` - `git rebase origin/main` ## Step 4: Commit (if changes) Always ensure you are on the PR branch before committing. Use Conventional Commits: - `feat:` new behavior - `fix:` bug fix - `refactor:` refactor only - `chore:` tooling/docs/cleanup - Prefer `./scripts/committer` for commits. One-line summary: imperative, concise. Body (if needed): why + risk/impact. ## Step 5: Push + PR - `git push -u origin ` - If skill invoked: you have permission to open the PR. - Read the changes (`git status/diff`, key files) to build a specific PR summary/changes/testing section. - Always provide a PR body using `.github/PULL_REQUEST_TEMPLATE.md`. - Prefer: `gh pr create --label --title "" --body-file <(printf "...")` - If PR already exists or `--fill` is required: `gh pr edit <number> --body "<body>"` - Use `gh pr view/diff` to inspect the PR state/diff. - Consider optional version bump labels (`version:bump-minor|version:bump-major`) based on change impact. Required labels: - `type/feature` - `type/fix` - `type/chore` - `type/skip-changelog` ## Step 6: CI check - Loop: `gh run list` → `gh run view <id>` → fix → push → repeat until green (usually 60–90s). - If CI returns qlty feedback, address it, then re-run. - Run `bin/ci --no-signoff` before pushing; after push, run `bin/ci`. ## PR Body Template (from `.github/PULL_REQUEST_TEMPLATE.md`) ``` ## Summary - ... ## Label Checklist **Required** — pick exactly one `type/` label: - [ ] `type/feature` — new functionality - [ ] `type/fix` — bug fix or correction - [ ] `type/chore` — maintenance, refactor, deps - [ ] `type/skip-changelog` — docs/CI, no user impact **Optional** — version bump (default: patch): - [ ] `version:bump-minor` — new feature (1.0 → 1.1) - [ ] `version:bump-major` — breaking change (1.0 → 2.0) ``` --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jandragsbaek) — claim your Tome and manage your conversions.