Official agent skill

Creating Description For Gh PR

by redis in redis/jedis

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.

OfficialMITAuto-check passedDevelopment

Install Creating Description For Gh PR

skills CLI
$ npx skills add redis/jedis --skill creating-description-for-gh-pr -a claude-code

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

GitHub CLI
$ gh skill install redis/jedis creating-description-for-gh-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/redis/jedis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/creating-description-for-gh-pr .claude/skills/creating-description-for-gh-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/

Facts

Skill name
creating-description-for-gh-pr
GitHub stars
12k
Token cost
~838 tokens
SKILL.md length
341 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Resolve branches → Diff → Analyze → …
  • Update a PR description
  • SKILL.md covers 1. Resolve branches, 2. Diff, 3. Analyze and 4. Output structure, plus 1 more section
  • Calls git and gh

What it does

Creating Description For Gh PR is an agent skill from redis/jedis, published by the product's own GitHub organization. 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. Use this whenever the user asks to write, generate, draft, or update a PR description or PR title from local branch changes — including phrasing like "summarize this diff into a PR description," "write a PR description for my current branch," "create a PR title and description," or any request to compare a base and target branch for PR purposes. Trigger even if…

Its SKILL.md is about 840 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 Redis, GitHub, Java and Git. The licence is MIT.

When your agent uses it

  • Update a PR description
  • PR title from local branch changes — including phrasing like summarize this diff into a PR description
  • Write a PR description for my current branch
  • Create a PR title and description

Example prompts

  • “summarize this diff into a PR description,”
  • “write a PR description for my current branch,”
  • “create a PR title and description,”
  • “/creating-description-for-gh-pr”

Workflow steps

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

  1. Resolve branches
  2. Diff
  3. Analyze
  4. Output structure
  5. Confirm

What it can do on your machine

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

Creating Description For Gh PR loads about 838 tokens when it runs. Until then it costs about 157 tokens; SKILL.md has 341 words of instructions outside code blocks.

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

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 redis/jedis at commit bb5f01d, republished under its MIT licence (© redis). 341 words, ~838 tokens.

Download SKILL.mdSave it as .claude/skills/creating-description-for-gh-pr/SKILL.md (or your agent's skills folder).
name
creating-description-for-gh-pr
description
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. Use this whenever the user asks to write, generate, draft, or update a PR description or PR title from local branch changes — including phrasing like "summarize this diff into a PR description," "write a PR description for my current branch," "create a PR title and description," or any request to compare a base and target branch for PR purposes. Trigger even if the user doesn't name specific branches; this skill knows how to default them.

PR Description Generator

Writes a GitHub PR title and description from the diff between two local git branches, focused on what reviewers need: purpose, key decisions/assumptions, behavioral or conceptual changes, and a brief testing note if relevant. Uses only standard git commands, so any agent can follow it.

1. Resolve branches

  • Both named → use as given.
  • Only one named → it's the base; target defaults to current branch.
  • None named → base defaults to main, then master if main doesn't exist (git branch --list). Only check these two names — no scanning other branches, no guessing. If neither exists, stop and ask. Target defaults to current branch (git branch --show-current).

State the resolved base/target before proceeding.

2. Diff

  • Confirm both branches exist (git branch --list <name>); stop if not.
  • git diff <base>...<target> and git log <base>..<target> --oneline
  • Empty diff → stop and say so, don't fabricate a description.

3. Analyze

From the diff/log, identify: purpose of the change; key decisions and trade-offs; assumptions the code relies on; behavioral changes (concrete: "X now rejects Y" not "changed validation"); conceptual/contract changes; breaking changes, new config/env vars, migrations; test changes (what new tests cover conceptually, why existing ones were adapted — not test-by-test).

Skip routine stuff (formatting, trivial renames). No file/line enumeration — write like explaining to a teammate, not a changelog.

4. Output structure

Write to prDescription.md (repo root, overwrite if exists):

markdown
# <Title — imperative, <70 chars>

## Summary
<2-3 sentences>

## Key Decisions & Assumptions
<bullets — omit if none>

## Behavioral / Conceptual Changes
<bullets, concrete — omit if none>

## Testing
<2-3 sentences, only if diff touches tests — omit otherwise, don't write "no tests">

## Notes
<breaking changes, follow-ups — omit if none>

Keep it brief (readable in under a minute, ~150-200 words total unless the change is genuinely large). Omit empty sections rather than padding them. Never fabricate testing details, tickets, or names not evidenced in the diff — flag uncertainty in Notes instead.

5. Confirm

After writing, give a short confirmation (don't reprint the file) and offer to run gh pr create --title "..." --body-file prDescription.md if gh is available. Include the provided/resolved base and target branch names into the suggested command as part of the suggestion. At the end, ask if the user wants to open the PR now and wait for confirmation before proceeding. If the user declines, stop and say the PR description is ready in prDescription.md.

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

Files

Just SKILL.md in .agents/skills/creating-description-for-gh-pr of redis/jedis.

Open the folder on GitHubat commit bb5f01d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in redis/jedis, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Creating Description For Gh 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.

Creating Description For Gh PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Creating Description For Gh PR this skillredis/jedis12k—~838Automated 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
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Pascal Editor PR Openerpascalorg/editor25k—~619Automated safety check: PassMIT

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
  • 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
  • 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 today
    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
  • Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from redis/jedis

  • Official

    Add or extend Redis commands in the Jedis client API — a new core command, a family of new commands, an extension to an existing command's options, or a module command (Search/TimeSeries/JSON/Bloom).

    12k GitHub stars~7.2k tokensUpdated today
    Auto-check: warnings

Categories

Questions about Creating Description For Gh PR

What does Creating Description For Gh PR do?

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. Creating Description For Gh PR is an agent skill from redis/jedis, published by the product's own GitHub organization.md in the repo root.

When should I use Creating Description For Gh PR?

Creating Description For Gh PR fits situations like: update a PR description; PR title from local branch changes — including phrasing like summarize this diff into a PR description; write a PR description for my current branch; create a PR title and description.

How do I install Creating Description For Gh PR in Claude Code?

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

How do I install Creating Description For Gh PR in Codex?

Run `npx skills add redis/jedis --skill creating-description-for-gh-pr -a codex`. Or copy the skill folder (.agents/skills/creating-description-for-gh-pr in redis/jedis) into .agents/skills/creating-description-for-gh-pr in your project. Codex loads it when a task matches its description.

Can I use Creating Description For Gh 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 redis/jedis --skill creating-description-for-gh-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/creating-description-for-gh-pr, .gemini/skills/creating-description-for-gh-pr, .github/skills/creating-description-for-gh-pr and .opencode/skills/creating-description-for-gh-pr in your project.

What does Creating Description For Gh PR need to run?

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

Does Creating Description For Gh 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 Creating Description For Gh 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 Creating Description For Gh PR use?

Creating Description For Gh PR 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 Creating Description For Gh PR use?

About 838 tokens (SKILL.md is roughly 3.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 Creating Description For Gh PR?

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

Who maintains Creating Description For Gh PR?

redis (a GitHub organization, an official publisher) maintains it in redis/jedis, which has 12,366 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

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