Skills Guide

Create a Pull Request

VerifiedCaution

Create a feature branch and open a pull request for the current changes using GitHub CLI.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
7/24/2026
Claude Code
#pull-request#git-workflow#github-cli#rust#branching

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Creates a feature branch named after the GitHub user, checks the Rust code with cargo fmt and clippy, commits, and opens a pull request targeting main.

Strengths

  • Runs the whole git/PR flow from a single user-invoked command
  • Enforces Rust formatting and lint checks (cargo fmt --check, clippy -D warnings) before committing
  • Deterministic branch naming using the <username>/<feature_name> format
  • Keeps the PR title short and the body brief, with no Test plan section or generated-by attribution

Limitations

  • Assumes a Rust workspace with a crates/ directory and main as the target branch
  • Ships a hardcoded username remap (adilhafeez → adil) that only fits one author
  • Runs no tests and no diff review before committing and pushing
When to use it

Use it when your changes are ready and you want them formatted, linted, committed, and turned into a PR in one step.

When not to use it

Avoid it on non-Rust repos, when the target branch is not main, or when the PR body needs a detailed test plan.

Security analysis

Caution
Quality score80/100

The skill uses legitimate developer tooling (gh, git, cargo) for its stated purpose and contains no destructive, obfuscated, or exfiltration behavior. However, it triggers network operations and pushes commits automatically, so it warrants caution rather than being classified as fully safe.

Findings
  • •Instructs execution of shell commands including `git commit`, `git push`, `gh api`, and cargo checks, which create remote side effects.
  • •Commits all changes and pushes a branch without any explicit secret-scanning or diff review step.
  • •Contains a hardcoded username remapping (`adilhafeez` to `adil`) that could produce unexpected branch names or attribution.
How this analysis is made

Examples

Open a PR for current changes
/pr
After finishing a feature
Create a feature branch from my current changes and open a pull request against main.
Ship a Rust fix
I've finished the parser fix — open a PR for it, making sure fmt and clippy pass first.

name: pr description: Create a feature branch and open a pull request for the current changes. disable-model-invocation: true user-invocable: true

Create a pull request for the current changes:

  1. Determine the GitHub username via gh api user --jq .login. If the login is adilhafeez, use adil instead.
  2. Create a feature branch using format <username>/<feature_name> — infer the feature name from the changes
  3. Run cd crates && cargo fmt --all -- --check and cd crates && cargo clippy --locked --all-targets --all-features -- -D warnings to verify Rust code is clean
  4. Commit all changes with a short, concise commit message (one line, no Co-Authored-By)
  5. Push the branch and create a PR targeting main

Keep the PR title short (under 70 chars). Include a brief summary in the body. Never include a "Test plan" section or any "Generated with Claude Code" attribution.

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

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-mryiqff8/SKILL.md' && test -s '.skill-downloads/create-a-pull-request-mryiqff8/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/create-a-pull-request-mryiqff8' '.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-mryiqff8'

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

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