Agent skill

Create Pull Request

by phantompane in phantompane/phantom

Create a GitHub pull request for the current repository. An agent skill from phantompane/phantom.

MITAuto-check passedDevelopment

Install Create Pull Request

skills CLI
$ npx skills add phantompane/phantom --skill create-pull-request -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install phantompane/phantom create-pull-request --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/phantompane/phantom.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/create-pull-request .claude/skills/create-pull-request && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-pull-request
GitHub stars
213
Token cost
~902 tokens
SKILL.md length
409 words
Files
2
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Create a GitHub pull request for the current repository. An agent skill from phantompane/phantom.

  • Works in 9 steps: Run git status -sb to identify the… → If the current branch is main or the… → Inspect the change set with git diff,… → …
  • The user asks to create
  • SKILL.md covers Workflow, PR Title, PR Body and Creation Rules, plus 1 more section
  • Calls git and gh

What it does

Create Pull Request is an agent skill from phantompane/phantom. Create a GitHub pull request for the current repository. Use when the user asks to create, open, submit, or prepare a PR, or says the current branch is ready for review. Check git status and branch state, create a branch if needed, review diffs and commits, ensure changes are committed and pushed, draft a reviewer-friendly title/body, and create the PR with GitHub tools or gh. Unless the user explicitly asks otherwise, create draft pull requests and never add a "[codex]" prefix to the PR title.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. It works with GitHub and Git. The repository describes itself as: A powerful CLI tool for seamless parallel development with Git worktrees. The licence is MIT.

When your agent uses it

  • The user asks to create
  • Says the current branch is ready for review

Example prompts

  • “[codex]”
  • “/create-pull-request”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Run git status -sb to identify the current branch and pending changes.
  2. If the current branch is main or the repository default branch, create or ask for an appropriate feature branch before committing or…
  3. Inspect the change set with git diff, git diff --staged, and relevant commit history such as git log --oneline --decorate --max-count=20.
  4. Run relevant validation or repository preflight checks when feasible. If validation is skipped or fails, record the exact reason for the…
  5. Commit all intended changes before PR creation. Do not include unrelated user changes unless the user explicitly asks.
  6. Push the branch to origin with upstream tracking if needed.
  7. Check whether the current head branch already has an open PR using a GitHub tool, gh pr view, or gh pr list --head . Report or update the…
  8. Read the repository PR template before drafting the body. Check common paths such as .github/pull_request_template.md…
  9. Create the PR with the available GitHub tool first. If no GitHub tool can create PRs, use gh pr create.

What it can do on your machine

Read from SKILL.md and the folder at commit e9c03a6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Pull Request loads about 902 tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 409 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~130
When it runs · the whole SKILL.md, loaded when a task matches
~902

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from phantompane/phantom at commit e9c03a6, republished under its MIT licence (© phantompane). 409 words, ~902 tokens.

Download SKILL.mdSave it as .claude/skills/create-pull-request/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
create-pull-request
description
Create a GitHub pull request for the current repository. Use when the user asks to create, open, submit, or prepare a PR, or says the current branch is ready for review. Check git status and branch state, create a branch if needed, review diffs and commits, ensure changes are committed and pushed, draft a reviewer-friendly title/body, and create the PR with GitHub tools or gh. Unless the user explicitly asks otherwise, create draft pull requests and never add a "[codex]" prefix to the PR title.

Create Pull Request

Workflow

Follow this sequence before opening a PR:

  1. Run git status -sb to identify the current branch and pending changes.
  2. If the current branch is main or the repository default branch, create or ask for an appropriate feature branch before committing or pushing.
  3. Inspect the change set with git diff, git diff --staged, and relevant commit history such as git log --oneline --decorate --max-count=20.
  4. Run relevant validation or repository preflight checks when feasible. If validation is skipped or fails, record the exact reason for the PR body.
  5. Commit all intended changes before PR creation. Do not include unrelated user changes unless the user explicitly asks.
  6. Push the branch to origin with upstream tracking if needed.
  7. Check whether the current head branch already has an open PR using a GitHub tool, gh pr view, or gh pr list --head <branch>. Report or update the existing PR instead of creating a duplicate.
  8. Read the repository PR template before drafting the body. Check common paths such as .github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE.md, and .github/PULL_REQUEST_TEMPLATE/*.md.
  9. Create the PR with the available GitHub tool first. If no GitHub tool can create PRs, use gh pr create.

PR Title

  • Write a concise title that matches the repository's convention.
  • Do not prefix the title with [codex], even if older PRs in the repository used that prefix.
  • Use the user-requested title when provided, but strip a leading [codex] prefix case-insensitively before creating the PR.
Show full SKILL.md (164 more words)Show less

PR Body

Use the repository PR template when present and fill out every applicable section. If no template exists, use:

markdown
## Summary

- ...

## Testing

- ...

Include enough context for reviewers to understand:

  • what changed
  • why it changed
  • notable implementation decisions or tradeoffs
  • validation performed, including exact commands and relevant results
  • any known gaps or follow-up work

Keep the body factual and specific. Do not overstate testing that was not run.

Creation Rules

  • Prefer creating a draft PR unless the user explicitly asks for a ready-for-review PR.
  • Prefer GitHub MCP/app tools when they can create the PR. Fall back to gh pr create when needed.
  • Use non-interactive commands where possible.
  • Confirm the base branch from repository context or user instruction. If uncertain, inspect the remote default branch before choosing.
  • Do not open a PR from main directly.
  • Do not create a PR with uncommitted intended changes unless the user asks only to draft PR text.
  • Do not modify, discard, or revert unrelated working-tree changes while preparing the PR.

Command Examples

bash
git status -sb
git diff
git diff --staged
git log --oneline --decorate --max-count=20
git push -u origin <branch>
gh pr view --json number,url,state,isDraft,title
gh pr list --head <branch>
bash
gh pr create --draft --base <base-branch> --head <branch> --title "<PR title>" --body-file "<body-file>"

© phantompane, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .codex/skills/create-pull-request of phantompane/phantom.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e9c03a6

Compare with similar skills

Create Pull Request next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Pull Request compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Pull Request this skillphantompane/phantom213—~902Automated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0

Similar skills

  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated yesterday
    DevelopmentAuto-check passed

Works with

Categories

Questions about Create Pull Request

What does Create Pull Request do?

Create a GitHub pull request for the current repository. An agent skill from phantompane/phantom. Create Pull Request is an agent skill from phantompane/phantom. Create a GitHub pull request for the current repository.

When should I use Create Pull Request?

Create Pull Request fits situations like: the user asks to create; says the current branch is ready for review.

How do I install Create Pull Request in Claude Code?

Run `npx skills add phantompane/phantom --skill create-pull-request -a claude-code`. Or copy the skill folder (.codex/skills/create-pull-request in phantompane/phantom) into .claude/skills/create-pull-request in your project. Claude Code loads it when a task matches its description.

How do I install Create Pull Request in Codex?

Run `npx skills add phantompane/phantom --skill create-pull-request -a codex`. Or copy the skill folder (.codex/skills/create-pull-request in phantompane/phantom) into .agents/skills/create-pull-request in your project. Codex loads it when a task matches its description.

Can I use Create Pull Request in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phantompane/phantom --skill create-pull-request -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-pull-request, .gemini/skills/create-pull-request, .github/skills/create-pull-request and .opencode/skills/create-pull-request in your project.

What does Create Pull Request need to run?

Going by SKILL.md and its folder, Create Pull Request needs the command-line tools its instructions call (git and gh).

Does Create Pull Request access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Create Pull Request safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Pull Request use?

Create Pull Request is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Pull Request use?

About 902 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Pull Request?

Skills that share tags, products or a category with Create Pull Request: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and PR Review State Fetch (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Pull Request?

phantompane (a GitHub organization) maintains it in phantompane/phantom, which has 213 GitHub stars. The repository was last updated on October 7, 2026.

Source: phantompane/phantom on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.