Create a Pull Request

VerifiedCaution

Create a pull request for the current branch on a Docusaurus/React/TypeScript repository.

Sby Skills Guide Bot
DevelopmentBeginner
7/22/2026
Claude Code
#pull-request#git#github-cli#conventional-commits#docusaurus

Recommended for

Automated summary

Generates and creates a pull request for the current branch of a Docusaurus site by analyzing commits and the diff against main.

Strengths

  • Reviews all commits since divergence from main, not just the latest one
  • Infers the appropriate conventional commit prefix from the nature of the changes
  • Produces a structured PR body with a summary and a test plan covering build, typecheck and lint
  • Delegates to the /commit skill when uncommitted changes are detected

Limitations

  • Tightly coupled to the Buddies of Budgie repo (yarn commands and main target are hardcoded)
  • Assumes the gh CLI is authenticated and the remote branch does not yet exist
When to use it

When you have finished work on a branch and want to quickly open a well-written PR against main.

When not to use it

For a repository using a different package manager, target branch, or a platform other than GitHub.

Security analysis

Caution
Quality score88/100

The skill is scoped to a legitimate git/gh pull-request workflow and contains no destructive, obfuscated, or secret-exfiltrating instructions. It intentionally pushes the current branch and creates a remote PR, so it has meaningful external side effects, but they are consistent with its stated purpose.

Findings
  • •Performs remote write operations: `git push -u origin HEAD` and `gh pr create`, publishing branch content and creating a PR.
How this analysis is made

Examples

Open a PR for a docs fix
Create a pull request for my current branch — I fixed a broken link on the installation page.
PR after committing changes
I have staged changes for a new dark mode toggle; commit them if needed and open a PR against main.
Review commits before PR
Look at all my commits since main and open a PR with a suitable title and test plan.

name: pr description: Create a pull request for the current branch disable-model-invocation: false allowed-tools: Bash(git *), Bash(gh pr create *), Skill(commit)

Create a Pull Request

You are creating a pull request for the current branch on Buddies of Budgie docs (Docusaurus / React / TypeScript site).

Step 1: Gather Context

Run these commands to understand the current state:

git status
git log --oneline main..HEAD
git diff main...HEAD --stat
git diff main...HEAD
git branch --show-current

If there are uncommitted changes, run the /commit skill first before proceeding.

Step 2: Determine PR Type

Based on the changes, choose the conventional commit prefix:

  • feat: - New feature or functionality
  • fix: - Bug fix
  • chore: - Maintenance, dependency updates, refactoring
  • docs: - Documentation content changes
  • refactor: - Code restructuring without behavior change

Step 3: Generate PR Content

Title format: <type>: <short description> (under 70 characters)

Body format:

## Summary

- <bullet point describing key change 1>
- <bullet point describing key change 2>
- <bullet point describing key change 3>

## Test plan

- [ ] `yarn build` completes successfully
- [ ] `yarn typecheck` passes
- [ ] `yarn lint` passes
- [ ] Verified locally with `yarn start`
- [ ] <additional specific test steps>

If any commits include Assisted-by trailers, note that in the PR description (e.g., "AI-assisted - see commit trailers for details").

Step 4: Create the PR

Push the branch and create the PR:

git push -u origin HEAD
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body content>
EOF
)"

Target branch: main (default)

Notes

  • Review all commits since divergence from main, not just the latest one
  • Ensure the title accurately reflects the overall change
  • Test plan should include yarn build, yarn typecheck, and yarn lint

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-mrwak8va/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-mrwak8va' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-a-pull-request-mrwak8va/download' --output '.skill-downloads/create-a-pull-request-mrwak8va/SKILL.md.part' && mv '.skill-downloads/create-a-pull-request-mrwak8va/SKILL.md.part' '.skill-downloads/create-a-pull-request-mrwak8va/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.

Tools declared by the author (check availability in your agent): Bash(git *), Bash(gh pr create *), Skill(commit)

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

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/create-a-pull-request-mrwak8va/SKILL.md' && test -s '.skill-downloads/create-a-pull-request-mrwak8va/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/create-a-pull-request-mrwak8va' '.claude/skills/pr'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/create-a-pull-request-mrwak8va'

openskills read 'create-a-pull-request-mrwak8va'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

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-mrwak8va/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