New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GitHub PR Description

by lucasvieirasilva in lucasvieirasilva/nx-plugins

Generates a GitHub Pull Request description for this repository from the commits on the current branch, filling in .github/PULLREQUESTTEMPLATE.md (Current Behavior / Expected Behavior / Related…

MITAuto-check passedDevelopment

Install GitHub PR Description

skills CLI
$ npx skills add lucasvieirasilva/nx-plugins --skill github-pr-description -a claude-code

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

GitHub CLI
$ gh skill install lucasvieirasilva/nx-plugins github-pr-description --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/lucasvieirasilva/nx-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/github-pr-description .claude/skills/github-pr-description && 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
github-pr-description
GitHub stars
153
Token cost
~1.4k tokens
SKILL.md length
713 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Generates a GitHub Pull Request description for this repository from the commits on the current branch, filling in .github/PULLREQUESTTEMPLATE.md (Current Behavior / Expected Behavior / Related…

  • Works in 5 steps: Find the base and current branch. The… → List the commits on the branch: run git… → Understand the actual change, don't just… → …
  • Write a PR / pull request description
  • SKILL.md covers When invoked, The template to fill, PR title and Output format, plus 1 more section
  • Calls git and gh

What it does

GitHub PR Description is an agent skill from lucasvieirasilva/nx-plugins. Generates a GitHub Pull Request description for this repository from the commits on the current branch, filling in .github/PULLREQUESTTEMPLATE.md (Current Behavior / Expected Behavior / Related Issue(s)). Use this whenever the user wants to open, draft, or write a PR / pull request description, asks for "the PR body", wants release notes from commits, or is about to run gh pr create — even if they don't mention the template by name.

Its SKILL.md is about 1.4k 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 GitHub, Python, TypeScript and Git. The licence is MIT.

When your agent uses it

  • Write a PR / pull request description
  • Asks for the PR body
  • Wants release notes from commits
  • Is about to run gh pr create — even if they dont mention the template by name

Example prompts

  • “the PR body”
  • “Use the github-pr-description skill to generate a GitHub Pull Request description for this repository from the commits on the current branch…”
  • “/github-pr-description”

Workflow steps

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

  1. Find the base and current branch. The base is main. Get the current branch with git branch --show-current. If the current branch is main…
  2. List the commits on the branch: run git log origin/main..HEAD --pretty=format:'%s%n%b' to get subjects and bodies. If origin/main is…
  3. Understand the actual change, don't just parrot commit subjects. Use git diff origin/main..HEAD --stat to see the scope, and look at the…
  4. Infer the issue number (for the Fixes # line), in this order
  5. Fill in the template (see below) and propose a PR title in Conventional Commits format.

What it can do on your machine

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

GitHub PR Description loads about 1.4k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 713 words of instructions outside code blocks.

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

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 lucasvieirasilva/nx-plugins at commit 477650d, republished under its MIT licence (© lucasvieirasilva). 713 words, ~1,368 tokens.

Download SKILL.mdSave it as .claude/skills/github-pr-description/SKILL.md (or your agent's skills folder).
name
github-pr-description
description
Generates a GitHub Pull Request description for this repository from the commits on the current branch, filling in .github/PULL_REQUEST_TEMPLATE.md (Current Behavior / Expected Behavior / Related Issue(s)). Use this whenever the user wants to open, draft, or write a PR / pull request description, asks for "the PR body", wants release notes from commits, or is about to run `gh pr create` — even if they don't mention the template by name.

You are a GitHub Pull Request description writer for the nx-plugins repository. When invoked, you produce a ready-to-paste PR description by reading the commits on the current branch and filling in the repo's PR template. The goal is a description the author can paste into the GitHub PR body (or pass to gh pr create --body) with little or no editing.

When invoked

  1. Find the base and current branch. The base is main. Get the current branch with git branch --show-current. If the current branch is main, ask the user which branch/base to compare instead — there's nothing to describe otherwise.

  2. List the commits on the branch: run git log origin/main..HEAD --pretty=format:'%s%n%b' to get subjects and bodies. If origin/main is missing or stale, fall back to git log main..HEAD. If the user asked for "the last N commits", use -n N.

  3. Understand the actual change, don't just parrot commit subjects. Use git diff origin/main..HEAD --stat to see the scope, and look at the diff of the key files when the commit messages are terse. The "Current/Expected Behavior" framing requires you to understand what was broken or missing and what it does now.

  4. Infer the issue number (for the Fixes # line), in this order:

    • From the branch name: branches are often named like issue-348 → issue #348. Patterns like fix/348-..., 348-..., or feat/issue-348 also yield #348.
    • From commit messages: a trailing Fixes #123, Closes #123, or (#123).
    • If you cannot find one, leave the line as Fixes # (just the prefix) so the author fills it in — do not invent a number.

  5. Fill in the template (see below) and propose a PR title in Conventional Commits format.

The template to fill

This repo's .github/PULL_REQUEST_TEMPLATE.md has three sections. Output exactly this structure, replacing the HTML comments with real content (keep the ## headings verbatim):

markdown
## Current Behavior

<describe how things behave today — the bug, gap, or limitation this PR addresses>

## Expected Behavior

<describe how things behave after this PR — what changed and the resulting behavior>

## Related Issue(s)

Fixes #<number>

Notes on each section:

  • Current Behavior — the problem state. For a bug, say what goes wrong (and how to reproduce it, if the diff makes that clear). For a feature, describe the gap/limitation that existed. If the change is a pure refactor or chore with no user-facing "bug", describe the prior implementation and why it was worth changing.
  • Expected Behavior — the new state after the PR. Be concrete about behavior, not just "fixed it": name the affected executor/generator/provider/area and what a user will now observe. A short bulleted list is fine when several things changed.
  • Related Issue(s) — keep the Fixes #<number> line. If there's no issue, leave Fixes #. If multiple issues, add one Fixes # line each.
Show full SKILL.md (294 more words)Show less

PR title

Propose a single-line title in Conventional Commits format, matching this repo's commit style (it uses commitizen / conventional commits): type(scope): summary.

  • Common types here: fix, feat, chore, docs, refactor, test, style, perf.
  • Scope is usually the package or area, e.g. nx-python, data-migration, release. Use the scope seen in the branch's commits when consistent.
  • Lowercase summary, imperative mood, no trailing period.

Example: fix(nx-python): update local dependency version ranges during release

If the branch is a single commit, the existing commit subject is usually a good title — reuse it unless it's vague.

Output format

Present the result in two clearly separated parts so the author can grab each:

  1. A Title: line with the proposed conventional-commit title.
  2. The PR body as a single markdown code block containing the filled template, so it pastes cleanly into GitHub or gh pr create --body "...".

After the description, if you had to leave Fixes # blank or guessed the issue number from the branch, say so in one short line so the author can confirm.

Rules and style

  • Base is always main. Don't compare against other branches unless the user explicitly asks.
  • Don't hard-wrap prose. GitHub renders markdown; keep each paragraph/bullet on one line and use blank lines between paragraphs. Don't insert mid-sentence newlines.
  • Write from the diff, not assumptions. Only describe behavior you can support from the commits/diff. It's better to be brief and correct than to pad with speculation.
  • Don't fabricate issue numbers. Inferring #348 from a branch named issue-348 is fine; making up a number is not.
  • Keep the three headings exactly as ## Current Behavior, ## Expected Behavior, ## Related Issue(s) so the output matches the repo template.
  • Offer to open the PR with gh pr create only if the user asks; by default just produce the description.

© lucasvieirasilva, 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 .claude/skills/github-pr-description of lucasvieirasilva/nx-plugins.

Open the folder on GitHubat commit 477650d

Compare with similar skills

GitHub PR Description 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.

GitHub PR Description compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub PR Description this skilllucasvieirasilva/nx-plugins153—~1.4kAutomated safety check: PassMIT
Skyvern Version BumpSkyvern-AI/skyvern23k—~1kAutomated safety check: NotesAGPL-3.0
GitHub Fork and PR Submissionjxxghp/MoviePilot12k—~1.1kAutomated safety check: NotesGPL-3.0
PR Review Comments Fetcherwarpdotdev/warp65k1 repos~1.1kAutomated safety check: PassAGPL-3.0
CodeScope Codebase Graph AnalysisQwenLM/qwen-code28k1 repos~9.3kAutomated safety check: PassApache-2.0
Smart PR ReviewLeoYeAI/openclaw-master-skills2.2k—~2.7kAutomated safety check: NotesMIT

Similar skills

  • Skyvern Version Bump

    Skyvern-AI/skyvern

    Walks through a Skyvern open-source release bump: update the version, rebuild the Python and TypeScript SDKs with Fern, commit, and open a pull request.

    23k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check: notes

  • GitHub Fork and PR Submission

    jxxghp/MoviePilot

    Submits code changes as a GitHub pull request through an isolated Git clone, reusing or creating your fork and pushing only after you confirm the real diff.

    12k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check: notes

  • PR Review Comments Fetcher

    warpdotdev/warp

    Pulls every review comment from the current branch's GitHub pull request into Warp's code review panel, then waits for your direction.

    65k GitHub starsUsed in 1 repo~1.1k tokens
    DevelopmentAuto-check passed

  • CodeScope Codebase Graph Analysis

    QwenLM/qwen-code

    Answers questions about code structure, history, bugs and PR risk using a CodeScope knowledge graph and semantic index built from the repository.

    28k GitHub starsUsed in 1 repo~9.3k tokens
    DevelopmentAuto-check passed

  • Smart PR Review

    LeoYeAI/openclaw-master-skills

    Opinionated AI code reviewer — not a yes-machine. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~2.7k tokensUpdated 2 mo ago
    DevelopmentAuto-check: notes

  • Datadog Data Source Generator

    DataDog/terraform-provider-datadog

    Official

    Generates a Datadog Terraform provider data source from an OpenAPI operation with tfgen and opens a review-ready GitHub PR with a risk scan and testing guide.

    468 GitHub stars~2.7k tokensUpdated today
    DevOps & CloudAuto-check passed

More from lucasvieirasilva/nx-plugins

  • Conventional Commit Message

    lucasvieirasilva/nx-plugins

    Writes a Conventional Commits message for staged changes in this repository, matching its commitlint config (@commitlint/config-conventional) and package-name scopes like nx-python / data-migration…

    153 GitHub stars~1.5k tokensUpdated 10 days ago
    Auto-check passed

  • Sonarcloud Review

    lucasvieirasilva/nx-plugins

    Fetches and triages SonarCloud findings (issues, security hotspots, quality gate) for the current pull request or branch of this repository via the SonarCloud Web API, summarizes them in a markdown…

    153 GitHub stars~2.7k tokensUpdated 10 days ago
    Auto-check: notes

Works with

Categories

Questions about GitHub PR Description

What does GitHub PR Description do?

Generates a GitHub Pull Request description for this repository from the commits on the current branch, filling in .github/PULLREQUESTTEMPLATE.md (Current Behavior / Expected Behavior / Related…. GitHub PR Description is an agent skill from lucasvieirasilva/nx-plugins.md (Current Behavior / Expected Behavior / Related Issue(s)).

When should I use GitHub PR Description?

GitHub PR Description fits situations like: write a PR / pull request description; asks for the PR body; wants release notes from commits; is about to run gh pr create — even if they dont mention the template by name.

How do I install GitHub PR Description in Claude Code?

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

How do I install GitHub PR Description in Codex?

Run `npx skills add lucasvieirasilva/nx-plugins --skill github-pr-description -a codex`. Or copy the skill folder (.claude/skills/github-pr-description in lucasvieirasilva/nx-plugins) into .agents/skills/github-pr-description in your project. Codex loads it when a task matches its description.

Can I use GitHub PR Description 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 lucasvieirasilva/nx-plugins --skill github-pr-description -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-pr-description, .gemini/skills/github-pr-description, .github/skills/github-pr-description and .opencode/skills/github-pr-description in your project.

What does GitHub PR Description need to run?

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

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

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

About 1.4k tokens (SKILL.md is roughly 5.5k 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 GitHub PR Description?

Skills that share tags, products or a category with GitHub PR Description: Skyvern Version Bump (Skyvern-AI/skyvern, 23k stars), GitHub Fork and PR Submission (jxxghp/MoviePilot, 12k stars), PR Review Comments Fetcher (warpdotdev/warp, 65k stars) and CodeScope Codebase Graph Analysis (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub PR Description?

lucasvieirasilva (a GitHub user) maintains it in lucasvieirasilva/nx-plugins, which has 153 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 28, 2026.

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