Agent skill

PR

Create a GitHub pull request from current working changes. An agent skill from reactive/data-client.

Apache-2.0Auto-check passedDevelopment

Install PR

skills CLI

$ npx skills add reactive/data-client --skill pr -a claude-code

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

GitHub CLI

$ gh skill install reactive/data-client 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/reactive/data-client.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr .claude/skills/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 "pr" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/pr into .claude/skills/pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/reactive/data-client/tree/master/.agents/skills/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 reactive/data-client --skill pr -a codex

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

GitHub CLI

$ gh skill install reactive/data-client 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/reactive/data-client.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pr .agents/skills/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 "pr" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/pr into .agents/skills/pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 reactive/data-client --skill pr -a cursor

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

GitHub CLI

$ gh skill install reactive/data-client 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/reactive/data-client.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pr .cursor/skills/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 "pr" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/pr into .cursor/skills/pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/reactive/data-client.git --path .agents/skills/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 reactive/data-client --skill pr -a gemini-cli

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

GitHub CLI

$ gh skill install reactive/data-client 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/reactive/data-client.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pr .gemini/skills/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 "pr" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/pr into .gemini/skills/pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 reactive/data-client 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 reactive/data-client --skill pr -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/reactive/data-client.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pr .github/skills/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 "pr" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/pr into .github/skills/pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 reactive/data-client --skill 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 reactive/data-client 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/reactive/data-client.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pr .opencode/skills/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 "pr" agent skill from https://github.com/reactive/data-client/tree/master/.agents/skills/pr into .opencode/skills/pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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: pr
GitHub stars: 2k
Token cost: ~1.2k tokens
SKILL.md length: 500 words
Files: 1
Skills in repo: 17
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Create a GitHub pull request from current working changes. An agent skill from reactive/data-client.

Works in 7 steps: Assess Git State → Handle Git States → Validate Changesets and Blog (before… → …
The user asks to create a PR
SKILL.md covers Overview, Step 1: Assess Git State, Step 2: Handle Git States and Step 3: Validate Changesets…, plus 4 more sections
Calls git and gh

What it does

PR is an agent skill from reactive/data-client. Create a GitHub pull request from current working changes. Handles all git states - uncommitted changes, no branch, unpushed commits, etc. Analyzes diffs and changesets to generate a PR with filled-in template. Opens the PR in the browser when done. Use when the user asks to create a PR, open a PR, submit changes, or push for review.

Its SKILL.md is about 1.2k 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 and Git workflow. It works with Git and GitHub. The repository describes itself as: Async State Management without the Management. REST, GraphQL, SSE, Websockets. The licence is Apache-2.0.

When your agent uses it

The user asks to create a PR
Push for review

Example prompts

“/pr”

Workflow steps

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

Assess Git State
Handle Git States
Validate Changesets and Blog (before committing)
Push to Remote
Analyze Changes for PR Description
Create the PR
Open in Browser

What it can do on your machine

Read from SKILL.md and the folder at commit 6d35253. 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

PR loads about 1.2k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 500 words of instructions outside code blocks.

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

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 reactive/data-client at commit 6d35253, republished under its Apache-2.0 licence (© reactive). 500 words, ~1,235 tokens.

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

name: pr
description: Create a GitHub pull request from current working changes. Handles all git states - uncommitted changes, no branch, unpushed commits, etc. Analyzes diffs and changesets to generate a PR with filled-in template. Opens the PR in the browser when done. Use when the user asks to create a PR, open a PR, submit changes, or push for review.
disable-model-invocation: true
metadata.internal: true

Create Pull Request

Overview

Analyze the current git state, prepare changes for a PR, create it on GitHub with a well-crafted description, and open it in the browser.

Step 1: Assess Git State

Run these commands in parallel to understand the current state:

bash

git status --porcelain
git branch --show-current
git log --oneline master..HEAD 2>/dev/null
git diff --stat master...HEAD 2>/dev/null
git stash list

Also check for existing PR on the current branch:

bash

gh pr view --json url,state 2>/dev/null

Step 2: Handle Git States

Based on the assessment, follow the appropriate path:

No changes anywhere

If working tree is clean AND no commits ahead of master → inform user there's nothing to PR.

On `master` with uncommitted changes only

Ask the user for a branch name, or infer one from the changes (lowercase, hyphenated, concise)
Create and switch to branch: git checkout -b <branch-name>
Stage all changes: git add -A
Analyze the diff and write a commit message following the project's conventional commit style (see Commit Style below)
Commit the changes

On `master` with commits ahead (not yet on a branch)

Ask the user for a branch name, or infer one
Create branch at current position: git checkout -b <branch-name>
(The commits come along automatically)

On feature branch with uncommitted changes

Stage all changes: git add -A
Analyze the diff and write a commit message
Commit the changes

On feature branch, all committed, not pushed

Continue to Step 3.

PR already exists

Inform the user and provide the existing PR URL. Ask if they want to update it instead.

Step 3: Validate Changesets and Blog (before committing)

For user-facing changes (feat:, fix:, enhance:), check that changesets and blog updates exist:

bash

ls .changeset/*.md 2>/dev/null | grep -v README
git diff --name-only master...HEAD 2>/dev/null
git status --porcelain

If changesets are missing or the draft blog post is unmodified, invoke the skill "changeset" to create them before proceeding. Skip this step for docs:, pkg:, internal:, demo: changes.

Step 4: Push to Remote

bash

git push -u origin HEAD

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

Step 5: Analyze Changes for PR Description

Gather information for the PR body:

bash

# Full diff against master
git diff master...HEAD

# Commit messages
git log --format='%s%n%n%b' master..HEAD

# Check for changesets
ls .changeset/*.md 2>/dev/null | grep -v README

Read any changeset files (.changeset/*.md, excluding README.md) — these contain curated descriptions of what changed and why. Use them as primary source material for the PR description.

Examine the diff to understand:

Which packages are affected
Whether there are test changes
Whether there are doc changes
The nature of the change (feature, fix, refactor, docs, internal, pkg)

Step 6: Create the PR

Use gh pr create with the project's PR template structure. Base branch is always master.

PR Title

Follow commit convention style:

feat: <description> — new feature
fix: <description> — bug fix
enhance: <description> - improvements
docs: <description> — documentation only
pkg: <description> — dependency updates
internal: <description> — internal tooling/infra
demo: <description> — example app changes

Scope is optional, used for specificity (e.g., feat(rest):, fix(core):). Use imperative mood, under 72 chars. If the PR spans multiple types, use the most significant one. Commit messages follow the same convention.

PR Body Template

Fill in the template based on the analyzed changes. Remove HTML comments. Leave sections empty with "N/A" if not applicable. The Fixes # line should be omitted if there's no linked issue.

markdown

Fixes #<issue number if known, otherwise remove this line>

### Motivation

<Why this change exists. Pull from changeset descriptions, commit messages, and diff analysis.
Be specific: does it solve a bug? Enable a new use-case? Improve DX?>

### Solution

<High-level description of what was done. Key technical decisions and their rationale.
Mention affected packages, architectural choices, trade-offs.>

### Open questions

<Any unresolved design questions, or "N/A" if none>

Create Command

bash

gh pr create --base master --title "<title>" --body "$(cat <<'EOF'
<body content>
EOF
)"

Capture the PR URL from the output.

Step 7: Open in Browser

bash

gh pr view --web

Files

Just SKILL.md in .agents/skills/pr of reactive/data-client.

Open the folder on GitHubat commit 6d35253

Compare with similar skills

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.

PR compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
PR this skillreactive/data-client	2k	—	~1.2k	Automated safety check: Pass	Apache-2.0	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Creating Description For Gh PRredis/jedis	12k	—	~838	Automated safety check: Pass	MIT	today
Create Pull Request with Work Item IDmakeplane/plane	61k	—	~824	Automated safety check: Pass	AGPL-3.0	today
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	yesterday

Similar skills

Contributor-First PR Merge
HKUDS/OpenHarness
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
Create Pull Request
cline/cline
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
Creating Description For Gh PR
redis/jedis
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 today
DevelopmentAuto-check passed
Create Pull Request with Work Item ID
makeplane/plane
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 today
DevelopmentAuto-check passed
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
57k GitHub stars~2.5k tokensUpdated yesterday
DevelopmentAuto-check passed
Pascal Editor PR Opener
pascalorg/editor
Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain.
25k GitHub stars~619 tokensUpdated today
DevelopmentAuto-check passed

Questions about PR

What does PR do?

Create a GitHub pull request from current working changes. An agent skill from reactive/data-client. PR is an agent skill from reactive/data-client. Create a GitHub pull request from current working changes.

When should I use PR?

PR fits situations like: the user asks to create a PR; push for review.

How do I install PR in Claude Code?

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

How do I install PR in Codex?

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

Can I use 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 reactive/data-client --skill 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/pr, .gemini/skills/pr, .github/skills/pr and .opencode/skills/pr in your project.

What does PR need to run?

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

Does PR 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 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 PR use?

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

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

Skills that share tags, products or a category with PR: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Creating Description For Gh PR (redis/jedis, 12k stars) and Create Pull Request with Work Item ID (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR?

reactive (a GitHub organization) maintains it in reactive/data-client, which has 2,037 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.

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

Install PR

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create Pull Request

Overview

Step 1: Assess Git State

Step 2: Handle Git States

No changes anywhere

On master with uncommitted changes only

On master with commits ahead (not yet on a branch)

On feature branch with uncommitted changes

On feature branch, all committed, not pushed

PR already exists

Step 3: Validate Changesets and Blog (before committing)

Step 4: Push to Remote

Step 5: Analyze Changes for PR Description

Step 6: Create the PR

PR Title

PR Body Template

Create Command

Step 7: Open in Browser

Files

Compare with similar skills

Similar skills

More from reactive/data-client

Related

Questions about PR

On `master` with uncommitted changes only

On `master` with commits ahead (not yet on a branch)