Skills Guide

Create or update a GitHub pull request

VerifiedCaution

Create or update a GitHub pull request following Medox conventions. Invoke manually with /pr.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/24/2026
Claude Code
#pull-request#github#git-workflow#code-review#mcp

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Creates or updates a GitHub pull request following Medox conventions, first checking whether an open PR already exists for the current branch.

Strengths

  • Detects an existing PR by listing pull requests filtered on the branch head before creating a new one, avoiding duplicates
  • Enforces a structured PR body with a summary, a checkbox test plan, and a generation footer
  • Syncs documentation by running /docs-up before the PR is created and automatically assigns the configured reviewer

Limitations

  • Tightly coupled to a specific setup (Medox conventions, spicode-bot author, spideystreet reviewer), so it is not directly reusable elsewhere
  • Requires the GitHub MCP server plus .claude/rules/git.md and the /docs-up skill, without which several steps fail
  • Marked manual-invocation only (/pr), so it will never fire on its own even when a PR would be useful
When to use it

Use it when a working branch is ready and you want to open or refresh a GitHub PR formatted to the team's conventions.

When not to use it

Avoid it on repositories that do not follow these conventions, or when no GitHub MCP server is configured.

Security analysis

Caution
Quality score76/100

The skill is a straightforward PR workflow helper. It does not contain destructive commands, secret exfiltration, obfuscated payloads, or safety-disabling instructions. It does use powerful tools (git push, gh CLI, GitHub MCP) for legitimate repository automation, and it mutates remote state (pushes branches, creates/edits PRs, assigns reviewers) without an explicit confirmation step, which warrants a caution rather than safe rating. It also defers to an external `/docs-up` skill and a `.claude/rules/git.md` file whose contents are unverified.

Findings
  • •Performs network/remote operations: `git push -u origin <branch>` and PR creation/editing via GitHub MCP tools and `gh pr edit`
  • •Auto-assigns a hardcoded reviewer and asserts an author identity (spideystreet / spicode-bot) without confirmation
  • •Chains into another skill (`/docs-up`) that is not defined here, so its behavior is unvetted from this file alone
  • •Depends on out-of-band conventions in `.claude/rules/git.md` that are not included in the package
How this analysis is made

Examples

Open a PR for the current branch
/pr — open a pull request for my current branch against main
Refresh an existing PR
/pr — my branch already has an open PR; update its title and body to reflect the new commits
PR with test plan
/pr and include a test plan with the pytest command and the manual checkout scenario I just validated

name: pr description: Create or update a GitHub pull request following Medox conventions (author spicode-bot, reviewer spideystreet). Invoke manually with /pr — do NOT trigger automatically. disable-model-invocation: true

Skill: Pull Request

Create or update a GitHub PR following the conventions defined in .claude/rules/git.md.

Steps

  1. Pre-flight: docs sync — run /docs-up first to ensure docs are up to date with code changes
  2. git log main..HEAD --oneline — review commits included
  3. Push if needed: git push -u origin <branch>
  4. Check if a PR already exists for the current branch:
    • Use mcp__github__list_pull_requests with head: "spideystreet:<branch>" and state: "open"
    • If a PR exists → update it (step 5b)
    • If no PR exists → create it (step 5a)

5a. Create PR

  • Use mcp__github__create_pull_request:
    • title: <type>(<scope>): <summary>
    • head: current branch
    • base: main
    • body: see Body format below
  • Add reviewer: gh pr edit <number> --add-reviewer spideystreet

5b. Update PR

  • Use gh pr edit <number> to update --title and/or --body if commits changed the scope
  • Push new commits (already done in step 3)
  • Report the existing PR URL to the user

Body format

## Summary

- <bullet points from commits>

## Test plan

- [ ] `uv run pytest <tests> -v`
- [ ] Manual: <scenario>

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

Rules

  • Always prefer GitHub MCP tools (mcp__github__*) over gh CLI for GitHub operations (create PR, list issues, add comments, etc.)
  • Use git CLI only for local operations (log, push, diff, status)
  • Use gh pr edit for updating title/body (no MCP equivalent)

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-or-update-a-github-pull-request-mryiqfkl/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-or-update-a-github-pull-request-mryiqfkl' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-or-update-a-github-pull-request-mryiqfkl/download' --output '.skill-downloads/create-or-update-a-github-pull-request-mryiqfkl/SKILL.md.part' && mv '.skill-downloads/create-or-update-a-github-pull-request-mryiqfkl/SKILL.md.part' '.skill-downloads/create-or-update-a-github-pull-request-mryiqfkl/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-or-update-a-github-pull-request-mryiqfkl/SKILL.md' && test -s '.skill-downloads/create-or-update-a-github-pull-request-mryiqfkl/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/create-or-update-a-github-pull-request-mryiqfkl' '.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-or-update-a-github-pull-request-mryiqfkl'

openskills read 'create-or-update-a-github-pull-request-mryiqfkl'

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-or-update-a-github-pull-request-mryiqfkl/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