Official agent skill

Create PR

Push the current branch and create a pull request against docker/docs.

OfficialApache-2.0Auto-check passedDevelopment

Install Create PR

skills CLI

$ npx skills add docker/docs --skill create-pr -a claude-code

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

GitHub CLI

$ gh skill install docker/docs create-pr --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/docker/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-pr .claude/skills/create-pr && 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/

Paste into Claude Code

Install the "create-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/create-pr into .claude/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/docker/docs/tree/main/.agents/skills/create-pr

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add docker/docs --skill create-pr -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install docker/docs create-pr --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/create-pr .agents/skills/create-pr && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "create-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/create-pr into .agents/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add docker/docs --skill create-pr -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install docker/docs create-pr --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/create-pr .cursor/skills/create-pr && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "create-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/create-pr into .cursor/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/docker/docs.git --path .agents/skills/create-pr

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add docker/docs --skill create-pr -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install docker/docs create-pr --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/create-pr .gemini/skills/create-pr && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "create-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/create-pr into .gemini/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install docker/docs create-pr

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add docker/docs --skill create-pr -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/create-pr .github/skills/create-pr && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "create-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/create-pr into .github/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add docker/docs --skill create-pr -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install docker/docs create-pr --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/create-pr .opencode/skills/create-pr && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "create-pr" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/create-pr into .opencode/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: create-pr
GitHub stars: 4.7k
Token cost: ~1.3k tokens
SKILL.md length: 542 words
Files: 1
Skills in repo: 13
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Push the current branch and create a pull request against docker/docs.

Works in 5 steps: Verify the branch → Push the branch → Create the PR → …
Tasks that involve Pull requests
SKILL.md covers 1. Verify the branch, 2. Push the branch, 3. Create the PR and 4. Apply labels and request…, plus 2 more sections
Calls gh and git

What it does

Create PR is an agent skill from docker/docs, published by the product's own GitHub organization. Push the current branch and create a pull request against docker/docs. Use after changes are committed and reviewed. "create a PR", "submit the fix", "open a pull request for this".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with Docker and Netlify. The repository describes itself as: Source repo for Docker's Documentation. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Pull requests

Example prompts

“create a PR”
“submit the fix”
“open a pull request for this”
“/create-pr”

Requirements

Docker

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Verify the branch
Push the branch
Create the PR
Apply labels and request review
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 65aa5cd. 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:
- gh
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, 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 PR loads about 1.3k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 542 words of instructions outside code blocks.

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

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 docker/docs at commit 65aa5cd, republished under its Apache-2.0 licence (© docker). 542 words, ~1,347 tokens.

Download SKILL.mdSave it as .claude/skills/create-pr/SKILL.md (or your agent's skills folder).

name: create-pr
description: Push the current branch and create a pull request against docker/docs. Use after changes are committed and reviewed. "create a PR", "submit the fix", "open a pull request for this".

Create PR

Push the branch and create a properly structured pull request.

1. Verify the branch

Confirm you're on a dedicated branch, not the default branch:

bash

git branch --show-current   # must not be main or master

If this returns main or master, stop. Create a branch and move your commits onto it before continuing.

Confirm commits exist and the working tree is clean:

bash

git log --oneline main..HEAD   # confirm commits exist
git status --porcelain         # must print nothing

If git status --porcelain prints anything, there are uncommitted or unstaged changes. Stop and commit them — or unstage stray files like package-lock.json — before opening a PR. Don't open a PR mid-edit.

2. Push the branch

Identify the remote that points at your fork. Inspect the remotes:

bash

git remote -v

If origin is your fork, use it. If origin points at canonical docker/docs (the upstream), push to your separate fork remote instead — never push the branch to docker/docs directly:

bash

FORK_REMOTE=origin   # or the name of your fork remote if origin is upstream
git push -u "$FORK_REMOTE" <branch-name>

3. Create the PR

Before creating a PR for an issue, check whether that issue already has an open linked PR:

bash

gh api repos/docker/docs/issues/<issue-number>/timeline --paginate \
  --jq '.[] | select((.event=="cross-referenced" or .event=="connected" or .event=="referenced") and .source.issue.pull_request and .source.issue.state=="open") | {url: .source.issue.html_url, title: .source.issue.title}'

If this returns an open PR that addresses the same issue, stop. Don't open a duplicate PR; report the existing PR instead. Only proceed if there is no open linked PR, or if the existing PR clearly does not address the issue and you explain why in the new PR body.

Derive the fork owner dynamically from the same fork remote you pushed to:

bash

FORK_OWNER=$(git remote get-url "$FORK_REMOTE" | sed -E 's|.*[:/]([^/]+)/[^/]+(\.git)?$|\1|')

bash

gh pr create --repo docker/docs \
  --head "${FORK_OWNER}:<branch-name>" \
  --title "<concise summary under 70 chars>" \
  --body "$(cat <<'EOF'
## Summary

<1-2 sentences: what was wrong and what was changed>

Closes #NNNN

Generated by <active coding agent name>
EOF
)"

Prefix the title with the change type to match repo convention — docs: for documentation changes (or another scope like hub: when appropriate), for example docs: fix broken link on install page.

Keep the body short. Reviewers need to know what changed and why — nothing else. Do not add a "Test plan" section — documentation PRs don't need one.

Use an accurate disclosure footer that names the active coding agent, for example Generated by Codex or Generated by Claude Code.

Show full SKILL.md (251 more words)Show less

Optional: Netlify preview entry path

If the PR primarily edits a single page or a focused section of pages, add a @netlify stanza to the PR body (for example, just below the Summary). This sets the entry path for the Netlify deploy preview so reviewers land on the edited page instead of the site root:

markdown

@netlify /desktop/setup/install/

The stanza takes a single published URL path. Derive it from the source file path: drop the content/ prefix and .md suffix, strip the /manuals segment, and add a trailing slash. For example, content/manuals/desktop/setup/install/mac-install.md becomes /desktop/setup/install/mac-install/.

Only add this when the change is focused on one page or section. Skip it for PRs that touch many unrelated pages — there is no useful single entry path.

Optional: Preview links

When the change is focused, also add direct links to the deploy preview in the PR body so reviewers can jump straight to the affected pages. The preview URL embeds the PR number:

https://deploy-preview-<pr-number>--docsdocker.netlify.app/path/to/page/

The PR number isn't known until gh pr create returns, so add these links after creating the PR by updating the body:

bash

gh pr edit <pr-number> --repo docker/docs --body "..."

Use the same source-path-to-URL mapping as the @netlify stanza above.

4. Apply labels and request review

Use the Issues API for labels — gh pr edit --add-label silently fails:

bash

gh api repos/docker/docs/issues/<pr-number>/labels \
  --method POST \
  --field 'labels[]=status/review'

Request review:

bash

gh pr edit <pr-number> --repo docker/docs --add-reviewer docker/docs-team

Verify the reviewer was assigned:

bash

gh pr view <pr-number> --repo docker/docs --json reviewRequests \
  --jq '.reviewRequests[].slug'

If the team doesn't appear, use the API directly:

bash

gh api repos/docker/docs/pulls/<pr-number>/requested_reviewers \
  --method POST --field 'team_reviewers[]=docs-team'

5. Report

Print the PR URL and current CI state:

bash

gh pr view <pr-number> --repo docker/docs --json url,state
gh pr checks <pr-number> --repo docker/docs --json name,state

Notes

Always use Closes #NNNN (not "Fixes") for GitHub auto-close linkage
One issue, one branch, one PR — never combine

Files

Just SKILL.md in .agents/skills/create-pr of docker/docs.

Open the folder on GitHubat commit 65aa5cd

Compare with similar skills

Create PR 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 PR compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create PR this skilldocker/docs	4.7k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
CI Act Runchewiebug/GCViewer	4.6k	—	~2.4k	Automated safety check: Notes	Custom licence	3 mo ago
Pull Requestwerf/werf	4.7k	—	~2.9k	Automated safety check: Pass	Apache-2.0	yesterday
Code ReviewAzure/Azurite	2.3k	—	~734	Automated safety check: Pass	MIT	yesterday
Review PRmicrosoft/vscode-containers	141	—	~900	Automated safety check: Pass	Custom licence	yesterday
ReleasePipelex/pipelex	939	—	~4.8k	Automated safety check: Notes	Custom licence	today

Similar skills

CI Act Run
chewiebug/GCViewer
Run the full build-and-deploy.yaml workflow locally via act + Docker.
4.6k GitHub stars~2.4k tokensUpdated 3 mo ago
DevelopmentAuto-check: notes
Pull Request
werf/werf
Generates Pull Request titles and descriptions according to werf conventions.
4.7k GitHub stars~2.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Code Review
Azure/Azurite
Official
Review Azurite pull requests with service-aware checks for Blob, Queue, and Table behavior, API compatibility, tests, and release notes.
2.3k GitHub stars~734 tokensUpdated yesterday
DevelopmentAuto-check passed
Review PR
microsoft/vscode-containers
Official
Review a specific vscode-containers pull request on demand from the CLI (or any interactive agent), the way a Container Tools maintainer would.
141 GitHub stars~900 tokensUpdated yesterday
DevelopmentAuto-check passed
Release
Pipelex/pipelex
Cut a release of pipelex, which ships the pipelex and pipelex-api packages and the pipelex/pipelex-api Docker image under one version: the gates, the migration-ledger cross-check, the CHANGELOG.md…
939 GitHub stars~4.8k tokensUpdated today
DevelopmentAuto-check: notes
Trailsnap Commit
LC044/TrailSnap
TrailSnap 仓库提交、推送、需求平台与 PR 工作流规则。Use when preparing commits, pushing branches, managing the corresponding platform requirement, creating or merging pull requests, or monitoring PR CI in this…
767 GitHub stars~557 tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Create PR

What does Create PR do?

Push the current branch and create a pull request against docker/docs. Create PR is an agent skill from docker/docs, published by the product's own GitHub organization. Push the current branch and create a pull request against docker/docs.

When should I use Create PR?

Create PR fits situations like: tasks that involve Pull requests.

How do I install Create PR in Claude Code?

Run `npx skills add docker/docs --skill create-pr -a claude-code`. Or copy the skill folder (.agents/skills/create-pr in docker/docs) into .claude/skills/create-pr in your project. Claude Code loads it when a task matches its description.

How do I install Create PR in Codex?

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

Can I use Create PR 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 docker/docs --skill create-pr -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-pr, .gemini/skills/create-pr, .github/skills/create-pr and .opencode/skills/create-pr in your project.

What does Create PR need to run?

Going by SKILL.md and its folder, Create PR needs the command-line tools its instructions call (gh and git). Our summary lists: Docker.

Does Create PR access the network?

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

Is Create PR 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 PR use?

Create PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create PR use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 PR?

Skills that share tags, products or a category with Create PR: CI Act Run (chewiebug/GCViewer, 4.6k stars), Pull Request (werf/werf, 4.7k stars), Code Review (Azure/Azurite, 2.3k stars) and Review PR (microsoft/vscode-containers, 141 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create PR?

docker (a GitHub organization, an official publisher) maintains it in docker/docs, which has 4,666 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

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

Install Create PR

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create PR

1. Verify the branch

2. Push the branch

3. Create the PR

Optional: Netlify preview entry path

Optional: Preview links

4. Apply labels and request review

5. Report

Notes

Files

Compare with similar skills

Similar skills

More from docker/docs

Related

Questions about Create PR