Agent skill

Write PR Description

by equinor in equinor/design-system

Write or revise a pull request description (title and body) for this repository.

MITAuto-check passedDevelopment

Install Write PR Description

skills CLI
$ npx skills add equinor/design-system --skill write-pr-description -a claude-code

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

GitHub CLI
$ gh skill install equinor/design-system write-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/equinor/design-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/write-pr-description .claude/skills/write-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
write-pr-description
GitHub stars
151
Token cost
~317 tokens
SKILL.md length
146 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Write or revise a pull request description (title and body) for this repository.

  • Works in 4 steps: Read the diff against the base branch… → Draft the title and body per § PR… → Check the draft against § Before… → …
  • Running gh pr create
  • Calls gh and git
  • The user asks for a PR description

What it does

Write PR Description is an agent skill from equinor/design-system. Write or revise a pull request description (title and body) for this repository. Use whenever opening a PR, running gh pr create or gh pr edit, or when the user asks for a PR description.

Its SKILL.md is about 320 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. The repository describes itself as: The Equinor design system. The licence is MIT.

When your agent uses it

  • Running gh pr create
  • The user asks for a PR description

Example prompts

  • “/write-pr-description”

Workflow steps

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

  1. Read the diff against the base branch (git diff origin/main...HEAD), the commit log (git log origin/main..HEAD) and the linked issue. If…
  2. Draft the title and body per § PR descriptions in the canonical doc, describing the final change.
  3. Check the draft against § Before posting. Count the prose and cut until it is within 300 words.
  4. Show the draft to the user. Run gh pr create or gh pr edit only after they approve it.

What it can do on your machine

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

Write PR Description loads about 317 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 146 words of instructions outside code blocks.

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

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 equinor/design-system at commit 35d1b25, republished under its MIT licence (© equinor). 146 words, ~317 tokens.

Download SKILL.mdSave it as .claude/skills/write-pr-description/SKILL.md (or your agent's skills folder).
name
write-pr-description
description
Write or revise a pull request description (title and body) for this repository. Use whenever opening a PR, running `gh pr create` or `gh pr edit`, or when the user asks for a PR description.

Write a PR description

Write a short PR description that lets a reviewer understand what changed, why, and how it was checked.

Canonical reference: documentation/agent-instructions/PR_AND_ISSUE_WRITING.md. Read it before drafting. It holds the word limit, the writing restrictions, the PR rules, an example and the checklist before posting. The title format is in AGENTS.md § Conventional Commits.

Steps

  1. Read the diff against the base branch (git diff origin/main...HEAD), the commit log (git log origin/main..HEAD) and the linked issue. If $ARGUMENTS names a PR number, read that PR with gh pr view instead.
  2. Draft the title and body per § PR descriptions in the canonical doc, describing the final change.
  3. Check the draft against § Before posting. Count the prose and cut until it is within 300 words.
  4. Show the draft to the user. Run gh pr create or gh pr edit only after they approve it.

© equinor, 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/write-pr-description of equinor/design-system.

Open the folder on GitHubat commit 35d1b25

Compare with similar skills

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

Write PR Description compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Write PR Description this skillequinor/design-system151—~317Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated 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
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k 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
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from equinor/design-system

  • Write Issue

    equinor/design-system

    Write or revise a GitHub issue (title and body) for this repository from notes, screenshots or a conversation.

    151 GitHub stars~362 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Write PR Description

What does Write PR Description do?

Write or revise a pull request description (title and body) for this repository. Write PR Description is an agent skill from equinor/design-system. Write or revise a pull request description (title and body) for this repository.

When should I use Write PR Description?

Write PR Description fits situations like: running gh pr create; the user asks for a PR description.

How do I install Write PR Description in Claude Code?

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

How do I install Write PR Description in Codex?

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

Can I use Write 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 equinor/design-system --skill write-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/write-pr-description, .gemini/skills/write-pr-description, .github/skills/write-pr-description and .opencode/skills/write-pr-description in your project.

What does Write PR Description need to run?

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

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

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

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

Skills that share tags, products or a category with Write PR Description: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write PR Description?

equinor (a GitHub organization) maintains it in equinor/design-system, which has 151 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.

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