Skills Guide

Create a Pull Request

VerifiedCaution

Commit changes, push the branch, and open a pull request on GitHub.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
7/22/2026
Claude Code
#git#pull-request#github#commit#code-review

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

This skill walks through opening a GitHub pull request: inspecting repo state, making a conventional commit, creating a branch, pushing, and creating the PR with gh.

Strengths

  • Runs git status / diff / log first to ground the agent in the actual changes
  • Enforces conventional commit format (type(scope): description) and a consistent branch naming scheme
  • Generates a structured PR body with a Type checklist, summary, bug details and test permalinks
  • Includes explicit safety rules: no git add -A, no direct pushes to main, no force push

Limitations

  • The label mapping table is hard-coded for one repo (Compass, Interaction) and needs editing elsewhere
  • Test links in the PR template point at the alamenai/terrae repository and must be replaced
  • Requires user confirmation before each step, which slows down fully automated runs
When to use it

Use it when a set of local changes needs to become a clean, correctly labeled GitHub pull request.

When not to use it

Avoid it on repositories that don't use GitHub, the gh CLI, or conventional commits, or where the template's labels don't match the project.

Security analysis

Caution
Quality score82/100

The skill is a straightforward git/GitHub PR workflow with no obfuscation, credential handling, curl|sh, or destructive commands. Its risk comes only from the powerful, legitimate operations it performs: committing, pushing branches, and creating PRs through unrestricted git/gh command patterns. It explicitly avoids staging secrets, avoids pushing to main, and discourages force pushes, so it is acceptable with normal user oversight.

Findings
  • •Publishes changes to a remote (git push -u origin) and opens public GitHub PRs via gh, which is an outward-facing action
  • •Requires interactive user confirmation only via instructions ('Ask user before proceeding'), not enforced by tooling
  • •Allows broad Bash(git *) / Bash(gh *) wildcards, so any git/gh subcommand is permitted, including history-rewriting ones (force push is discouraged only by prose)
How this analysis is made

Examples

Ouvrir une PR depuis des changements locaux
J'ai terminé mes modifications sur le composant de comparaison de code. Peux-tu committer, pousser la branche et ouvrir une pull request sur GitHub ?
Fix branch with bug report
I just fixed the marker cleanup bug. Commit the changes on a fix/ branch and open a PR with the bug details section filled in.
Label the PR
Open a pull request for my staged changes on the compass scope, commit message feat(compass): add new overview, and add the right type and component labels.

name: pr description: Commit, push, and open a pull request on GitHub allowed-tools: Bash(git *), Bash(gh *)

Pull Request Skill

Commit changes, push the branch, and open a pull request on GitHub.

Instructions

  1. Check Current State

    • Run git status to see changed files
    • Run git diff --staged and git diff to see all changes
    • Run git log --oneline -5 to see recent commits

  2. Stage and Commit

    • Stage specific files by name (avoid git add -A or git add .)
    • Never stage sensitive files (.env, credentials, etc.)
    • Follow conventional commit format: type(scope): description
    • Keep commit messages concise (under 72 characters)

  3. Create or Use Branch

    • If on main, create a new branch: git checkout -b <branch-name>
    • Branch name format: type/short-description (e.g., feat/code-comparison, fix/marker-cleanup)
    • If already on a feature branch, use it

  4. Push to Remote

    • Push with upstream tracking: git push -u origin <branch-name>

  5. Assign Labels Add --label flags to gh pr create based on the PR type and scope.

    Type labels — pick based on the commit type: | Commit type | Label | |-------------|-------| | fix | bug | | feat | enhancement | | docs | documentation | | test | (no type label) | | refactor | (no type label) | | chore | (no type label) |

    Component labels — if the scope matches a component label in the repo, add it: | Scope | Label | |-------|-------| | compass | Compass | | interaction | Interaction |

    Run gh label list to check available labels if unsure. Multiple labels can be combined:

    gh pr create --label "bug" --label "Compass" ...

  6. Open Pull Request

    • Use gh pr create to open the PR
    • Write a clear title (under 70 characters)
    • Write a description that follows the structure below based on PR type
    • Start with a Type checklist — check the one that applies:
    gh pr create --title "type(scope): description" --label "label" --body "$(cat <<'EOF'
## Type

- [ ] Feature
- [ ] Bug fix
- [ ] Refactor
- [ ] Test
- [ ] Docs
- [ ] Chore

## Summary
- bullet points describing what changed and why

## Bug Details (only for bug fixes)
**What was the bug?**
Describe the incorrect behavior.

**Why did it happen?**
Explain the root cause.

**How was it fixed?**
Describe the solution.

## Test Coverage
If tests were added or updated, link to the file on the branch (permalink):
- [`src/registry/map/__tests__/component.test.tsx`](https://github.com/alamenai/terrae/blob/<branch-name>/src/registry/map/__tests__/component.test.tsx)
EOF
)"

  7. Verify and Report

    • Show the PR URL to the user
    • Run git status to confirm clean state

Important Rules

  • Do NOT push to main directly — always use a feature branch
  • Do NOT force push unless explicitly requested
  • Ask user before proceeding with each step

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

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

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

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