Agent skill

Writing PR Description

by saleor in saleor/apps

A skill your agent uses when asked to create a pull request, write a PR description, or update/rewrite an existing PR description.

Custom licenceAuto-check passedDevelopment

Install Writing PR Description

skills CLI
$ npx skills add saleor/apps --skill writing-pr-description -a claude-code

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

GitHub CLI
$ gh skill install saleor/apps writing-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/saleor/apps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/writing-pr-description .claude/skills/writing-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
writing-pr-description
GitHub stars
162
Token cost
~630 tokens
SKILL.md length
354 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when asked to create a pull request, write a PR description, or update/rewrite an existing PR description.

  • Works in 3 steps: Gather context → Resolve the problem → Structure
  • Asked to create a pull request
  • SKILL.md covers 1. Gather context, 2. Resolve the problem, 3. Structure and Rules
  • Calls gh and git

What it does

Writing PR Description is an agent skill from saleor/apps. Use when asked to create a pull request, write a PR description, or update/rewrite an existing PR description.

Its SKILL.md is about 630 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 and Sentry. The repository describes itself as: OSS mirror for public Saleor Apps.

When your agent uses it

  • Asked to create a pull request
  • Write a PR description
  • Update/rewrite an existing PR description

Example prompts

  • “/writing-pr-description”

Workflow steps

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

  1. Gather context
  2. Resolve the problem
  3. Structure

What it can do on your machine

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

Writing PR Description loads about 630 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 354 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 354 words (~630 tokens).

“Combine commits and prompts into one statement: what problem does this PR solve, and why now? Commits describe steps; the description describes the outcome. Drop dead ends, reverted attempts and fixup commits.”

— opening of SKILL.md by saleor, Custom licence
name
writing-pr-description

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/writing-pr-description of saleor/apps.

Open the folder on GitHubat commit 4400af6

Compare with similar skills

Writing 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.

Writing PR Description compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing PR Description this skillsaleor/apps162—~630Automated safety check: PassCustom licence
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0
PR Writersickn33/agentic-awesome-skills47k2 repos~1.4kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT

Similar skills

  • 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 2 days ago
    DevelopmentAuto-check passed
  • PR Writer

    sickn33/agentic-awesome-skills

    Create pull requests following Sentry's engineering practices.

    47k GitHub starsUsed in 2 repos~1.4k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • 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

More from saleor/apps

  • Scaffold a new shared package in the saleor-apps monorepo under ./packages/.

    162 GitHub stars~608 tokensUpdated 4 days ago
    Auto-check passed
  • A skill your agent uses when adding a changeset, writing changelog or release notes, or when a functional change (feature, fix) is ready to commit.

    162 GitHub stars~514 tokensUpdated 4 days ago
    Auto-check passed
  • A skill your agent uses when writing or editing GraphQL operations (queries, mutations, fragments, webhook subscriptions) in a Saleor app — adding a .graphql file, adding fields to an existing one…

    162 GitHub stars~544 tokensUpdated 4 days ago
    Auto-check passed
  • Saleor App UI

    saleor/apps

    Styling and layout guide for Saleor Apps using modern macaw-ui and @saleor/apps-ui-next.

    162 GitHub stars~5.8k tokensUpdated 4 days ago
    Auto-check passed
  • Pinact

    saleor/apps

    Read pinact's documentation with pinact docs list and pinact docs show <name before answering.

    162 GitHub stars~685 tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Writing PR Description

What does Writing PR Description do?

A skill your agent uses when asked to create a pull request, write a PR description, or update/rewrite an existing PR description. Writing PR Description is an agent skill from saleor/apps. Use when asked to create a pull request, write a PR description, or update/rewrite an existing PR description.

When should I use Writing PR Description?

Writing PR Description fits situations like: asked to create a pull request; write a PR description; update/rewrite an existing PR description.

How do I install Writing PR Description in Claude Code?

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

How do I install Writing PR Description in Codex?

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

Can I use Writing 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 saleor/apps --skill writing-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/writing-pr-description, .gemini/skills/writing-pr-description, .github/skills/writing-pr-description and .opencode/skills/writing-pr-description in your project.

What does Writing PR Description need to run?

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

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

Writing PR Description has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Writing PR Description use?

About 630 tokens (SKILL.md is roughly 2.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 Writing PR Description?

Skills that share tags, products or a category with Writing PR Description: Create Pull Request with Work Item ID (makeplane/plane, 61k stars), PR Writer (sickn33/agentic-awesome-skills, 47k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Check PR (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing PR Description?

saleor (a GitHub organization) maintains it in saleor/apps, which has 162 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

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