How do I install the Create Pr skill?

Run npx skillmds@latest add tomevault-io/create-pr-24 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Pr?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Pr by tomevault-io — Agent Skill

Name: Create Pr
Author: tomevault-io

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.

tomevault-io Updated Sep 17, 2026

File contents

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: <type>/<topic>-<short-detail>, 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 <branch> origin/main

Existing branch:

git checkout <branch>
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 <branch>
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 <type> --title "<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 — claim your Tome and manage your conversions.

---name: create-pr-24description: 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.---# Create PR## OverviewFast, 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: `<type>/<topic>-<short-detail>`, 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 branchNew branch:- `git checkout -b <branch> origin/main`Existing branch:- `git checkout <branch>`- `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 <branch>`- 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 <type> --title "<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.

Frequently asked questions