Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From create-pr
Create a GitHub PR from the current feature branch. Auto-detects base branch, learns PR conventions from recent PRs, and generates a concise summary with a review guide. Use when asked to "create a PR", "open a PR", "make a pull request", or "submit PR".
npx claudepluginhub byunk/skills --plugin create-prHow this skill is triggered — by the user, by Claude, or both
Slash command
/create-pr:create-prSonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a GitHub PR from the current branch with a convention-aware title and body.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Create a GitHub PR from the current branch with a convention-aware title and body.
Confirm the working tree is on a feature branch and has commits to submit.
git branch --show-current
gh pr view --json baseRefName -q .baseRefName (existing PR or draft).gh repo view --json defaultBranchRef -q .defaultBranchRef.name.main.git fetch origin <base> --quiet.git rev-list --count origin/<base>..HEAD.If the current branch is the base branch, or there are zero commits ahead and no uncommitted changes, output "Nothing to submit — no commits ahead of base branch." and stop.
If there are uncommitted changes, warn the user that uncommitted changes will not be included in the PR and ask if they want to continue.
Examine recent merged PRs to understand the repo's PR style.
gh pr list --state merged --limit 5 --json title,body,number
Analyze the returned PRs for:
feat:, fix:, [JIRA-123]), capitalization, lengthIf no merged PRs exist or the repo is new, use a sensible default (concise summary + review guide).
Remember these conventions — you will apply them in Step 4.
Collect the information needed to write the PR content.
git log --oneline origin/<base>..HEAD
git log --format="%h %s%n%n%b" origin/<base>..HEAD
git diff origin/<base>...HEAD
git diff --stat origin/<base>...HEAD
For large diffs (more than 2000 lines), focus on the --stat output and read individual changed files selectively to understand the key changes.
Using the conventions from Step 2 and the changes from Step 3, generate:
Structure the body with these two sections (adapt naming if the repo uses different conventions):
## Summary
<One paragraph per distinct concept (e.g., new feature, refactoring, bug fix).
Separate paragraphs with a blank line. Each paragraph should be 1-2 sentences.>
## Review guide
- **Start here**: `path/to/key-file.ext` — <why this is the core change>
- <1-2 additional pointers to important files or design decisions>
Rules:
git push -u origin <current-branch>
gh pr create --base <base-branch> --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
gh pr create.If gh pr create fails, report the error and stop.