Skills Guide

Create a Pull Request

VerifiedCaution

Verify build and tests, generate a Conventional Commits title and body, then open a PR via gh pr create, including stacked PR handling.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
9/18/2026
Claude Code
#pull-request#git#github-cli#conventional-commits#stacked-prs

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Creates a GitHub pull request after verifying that the build and tests pass, generating a Conventional Commits title and a structured body through gh pr create.

Strengths

  • Chains build, test and diff review before any PR is created, and stops on failure
  • Auto-generates a Conventional Commits title plus a body with summary and test plan
  • Carefully documents the stacked-PR trap around --delete-branch and offers two safe sequences

Limitations

  • Assumes a Makefile exposing make build and make test targets, so other build tools need adaptation
  • Requires an authenticated gh CLI and defaults to the main base branch
  • Stacked-PR handling relies on manual commands outside the main flow
When to use it

Use it when a branch is ready and you want to open a GitHub PR knowing the build and tests are green.

When not to use it

Avoid it on non-GitHub repositories, without make build/make test targets, or when the PR body must be hand-crafted with very specific content.

Security analysis

Caution
Quality score88/100

The skill performs standard pull request workflows with git and gh, but includes potentially disruptive operations such as admin merges, branch deletion, history rewriting, and force pushes. These are legitimate for the described stacked PR scenarios but warrant caution due to their power.

Findings
  • •Uses `gh pr merge --admin --delete-branch`, which can bypass branch protection and delete branches.
  • •Uses `git push --force-with-lease` and `git rebase --onto`, which rewrite history and can disrupt shared branches.
  • •Runs arbitrary `make build` and `make test` targets from the repository without declaring allowed tools.
How this analysis is made

Examples

Open a PR for the current branch
Run /pr to verify the build and tests pass, then create a pull request for my current branch against main.
Stacked PR merge safety
PR B is stacked on PR A's branch. Before you merge PR A with --delete-branch, retarget PR B so it isn't auto-closed.

description: "Create a PR. Verify build and test pass, then run gh pr create" user-invokable: true

/pr

A skill for creating Pull Requests.

Steps

  1. Build verification: Run make build and confirm no errors
  2. Run tests: Run make test and confirm all tests pass
  3. Review diff: Check changes with git diff main...HEAD
  4. Generate PR title: Create a title in Conventional Commits format (feat(scope): description)
  5. Generate PR body: Generate body including a summary of changes and test plan
  6. Create PR: Run gh pr create --title "<title>" --body "<body>"
  7. Display result: Show the PR URL

PR Body Template

## Summary
- <bulleted list of changes>

## Test plan
- [ ] Test items

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Notes

  • If build or tests fail, do not create the PR and report the problem instead
  • Default base branch is main

Stacked PRs

When PR B is stacked on PR A's branch (B.base == A.head_branch) and you merge PR A with gh pr merge --delete-branch, GitHub auto-closes PR B because its base branch no longer exists. Auto-closed PRs cannot be reopened (gh pr reopen returns "Could not open the pull request") nor have their base changed (gh pr edit --base returns "Cannot change the base branch of a closed pull request").

Two safe sequences:

  1. Retarget before merging upstream (preferred when you have time):

    gh pr edit <B>  --base <A's base>     # B will temporarily show A's diff too — fine if A merges first
gh pr merge <A> --squash --admin --delete-branch

  2. Recreate downstream after merging upstream:

    gh pr merge <A> --squash --admin --delete-branch     # closes B
# in a worktree on B's branch:
git rebase --onto origin/<base> <A's-original-head-commit>     # drops A's commits, replays only B's
git push --force-with-lease
gh pr create --base <base> --head <B's-branch>

Do not use --delete-branch on the upstream PR if the downstream has not been retargeted — you lose the PR thread (closed PRs are still readable but lose OPEN semantics for review-gate and merge-queue tooling).

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-a-pull-request-mu6guoki/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-a-pull-request-mu6guoki' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-a-pull-request-mu6guoki/download' --output '.skill-downloads/create-a-pull-request-mu6guoki/SKILL.md.part' && mv '.skill-downloads/create-a-pull-request-mu6guoki/SKILL.md.part' '.skill-downloads/create-a-pull-request-mu6guoki/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-a-pull-request-mu6guoki/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot