How do I install the Create Pr skill?

Run npx skillmds@latest add zjgulai/create-pr 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. 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?

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

Create Pr by zjgulai — Agent Skill

Name: Create Pr
Author: zjgulai

Create Pr

Package code changes into reviewable, mergeable, communicable pull requests with proper title, description, scope, test results, risks, screenshots, and rollback notes. Use whenever local changes need to land on remote as a PR a human reviewer can actually approve.

zjgulai b99b55f 2.5 KB Updated Sep 17, 2026

File contents

create-pr

When the user asks to create a PR, you produce a PR a senior reviewer can approve without back-and-forth.

Pre-flight (mandatory checks, no exceptions)

Branch state: not on default branch (main/master), no uncommitted changes (or stash/commit first)
Remote tracking: branch pushed to remote with upstream set (-u)
CI/tests: relevant tests pass locally (note pre-existing failures, do NOT silently ignore)
Diff scope: review git diff <base>...HEAD yourself before drafting the PR

PR title

Format: <type>(<scope>): <imperative summary>

type ∈ feat | fix | refactor | docs | test | chore | perf | ci
scope is the touched module / area, not the file path
summary in imperative mood, ≤ 72 chars, no period

Examples:

feat(auth): add JWT refresh-token rotation
fix(ui): clamp progress bar to 0..100

PR body template

## Summary

<2-3 bullet points: what changed, why now>

## Changes

<concrete list — modules, key behaviors, schema migrations>

## Verification

- Tests run: `<command>` → `<result>`
- Manual verification: `<what the reviewer should reproduce>`
- Pre-existing failures: `<list, or "none">`

## Risks & rollback

- Risk: `<what could go wrong>`
- Rollback: `<git revert <sha>` or feature flag>

## Screenshots / recordings

<for UI changes; omit otherwise>

## Checklist

- [ ] Tests pass locally
- [ ] No secrets, tokens, or credentials in diff
- [ ] Migrations are forward-only or have explicit rollback path
- [ ] Breaking changes called out in summary

Rules

Never use git commit --no-verify or gh pr create --draft to silence pre-commit hooks
Never force-push to a branch with an open PR unless you wrote the PR yourself in this session
Always include a Verification section with at least one runnable command
Always call out pre-existing failures explicitly so reviewers don't assume you broke them

Workflow (when invoked)

git status → confirm clean / staged
git log <base>..HEAD --oneline → enumerate commits
git diff <base>...HEAD → understand scope
Draft title + body using templates above
gh pr create --title "..." --body "$(cat <<'EOF' ... EOF)" (HEREDOC for formatting)
Print PR URL on completion

---name: create-prdescription: Package code changes into reviewable, mergeable, communicable pull requests with proper title, description, scope, test results, risks, screenshots, and rollback notes. Use whenever local changes need to land on remote as a PR a human reviewer can actually approve.---# create-prWhen the user asks to create a PR, you produce a PR a senior reviewer can approve **without back-and-forth**.## Pre-flight (mandatory checks, no exceptions)1. **Branch state**: not on default branch (`main`/`master`), no uncommitted changes (or stash/commit first)2. **Remote tracking**: branch pushed to remote with upstream set (`-u`)3. **CI/tests**: relevant tests pass locally (note pre-existing failures, do NOT silently ignore)4. **Diff scope**: review `git diff <base>...HEAD` yourself before drafting the PR## PR titleFormat: `<type>(<scope>): <imperative summary>`- `type` ∈ `feat | fix | refactor | docs | test | chore | perf | ci`- `scope` is the touched module / area, not the file path- summary in imperative mood, ≤ 72 chars, no periodExamples:- `feat(auth): add JWT refresh-token rotation`- `fix(ui): clamp progress bar to 0..100`## PR body template```markdown## Summary<2-3 bullet points: what changed, why now>## Changes<concrete list — modules, key behaviors, schema migrations>## Verification- Tests run: `<command>` → `<result>`- Manual verification: `<what the reviewer should reproduce>`- Pre-existing failures: `<list, or "none">`## Risks & rollback- Risk: `<what could go wrong>`- Rollback: `<git revert <sha>` or feature flag>## Screenshots / recordings<for UI changes; omit otherwise>## Checklist- [ ] Tests pass locally- [ ] No secrets, tokens, or credentials in diff- [ ] Migrations are forward-only or have explicit rollback path- [ ] Breaking changes called out in summary```## Rules- **Never** use `git commit --no-verify` or `gh pr create --draft` to silence pre-commit hooks- **Never** force-push to a branch with an open PR unless you wrote the PR yourself in this session- **Always** include a `Verification` section with at least one runnable command- **Always** call out pre-existing failures explicitly so reviewers don't assume you broke them## Workflow (when invoked)1. `git status` → confirm clean / staged2. `git log <base>..HEAD --oneline` → enumerate commits3. `git diff <base>...HEAD` → understand scope4. Draft title + body using templates above5. `gh pr create --title "..." --body "$(cat <<'EOF' ... EOF)"` (HEREDOC for formatting)6. Print PR URL on completion

Frequently asked questions