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

Official agent skill

PR Body

by SAP in SAP/spartacus

A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.

OfficialApache-2.0Auto-check passedDevelopment

Install PR Body

skills CLI
$ npx skills add SAP/spartacus --skill pr-body -a claude-code

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

GitHub CLI
$ gh skill install SAP/spartacus pr-body --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/SAP/spartacus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr-body .claude/skills/pr-body && 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
pr-body
GitHub stars
784
Token cost
~499 tokens
SKILL.md length
240 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.

  • Works in 3 steps: Find the Jira ID. Read the current… → Gather the changes. Diff the branch… → Write the body in this exact structure
  • The user asks to generate
  • SKILL.md covers Steps, Writing the summary and Output format
  • Calls git; reaches jira.tools.sap

What it does

PR Body is an agent skill from SAP/spartacus, published by the product's own GitHub organization. Use this skill when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch. Triggers on requests like 'write a PR body', 'generate PR description', or 'create the PR description'.

Its SKILL.md is about 500 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 Git and Jira. The repository describes itself as: Spartacus is a lean, Angular-based JavaScript storefront for SAP Commerce Cloud that communicates exclusively through the Commerce REST API. The licence is Apache-2.0.

When your agent uses it

  • The user asks to generate
  • Draft a pull request (PR) body
  • Description for the current branch
  • Requests like write a PR body

Example prompts

  • “write a PR body”
  • “generate PR description”
  • “create the PR description”
  • “/pr-body”

Workflow steps

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

  1. Find the Jira ID. Read the current branch name (git rev-parse --abbrev-ref HEAD) and
  2. Gather the changes. Diff the branch against its base branch (usually develop) to see
  3. Write the body in this exact structure

What it can do on your machine

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

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • jira.tools.sap

    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 Body loads about 499 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 240 words of instructions outside code blocks.

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

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 SAP/spartacus at commit 38b4848, republished under its Apache-2.0 licence (© SAP). 240 words, ~499 tokens.

Download SKILL.mdSave it as .claude/skills/pr-body/SKILL.md (or your agent's skills folder).
name
pr-body
description
Use this skill when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch. Triggers on requests like 'write a PR body', 'generate PR description', or 'create the PR description'.

Generate a PR body

Produce a pull request description for the current branch.

Steps

  1. Find the Jira ID. Read the current branch name (git rev-parse --abbrev-ref HEAD) and extract the Jira ID — a substring shaped like CXSPA-xxxxx (a project key in capitals, a hyphen, then digits). If the branch has no such substring, leave the placeholder <jira_id> in the link and tell the user you couldn't find one.

  2. Gather the changes. Diff the branch against its base branch (usually develop) to see what changed, e.g. git diff --stat $(git merge-base develop HEAD) HEAD and git log $(git merge-base develop HEAD)..HEAD --oneline.

  3. Write the body in this exact structure:

    • First line, always:

      Closes: https://jira.tools.sap/browse/<jira_id>

      (replace <jira_id> with the extracted ID, e.g. CXSPA-13999)

    • A blank line, then a short summary of what the branch changes.

Writing the summary

  • Keep it simple and plain — describe what changed and why, from a user/reviewer point of view.
  • Avoid technical jargon, file paths.
  • Do not include any links or URLs in the summary. The only link allowed in the whole body is the Closes: line at the top.
  • A few short bullet points or a couple of sentences is enough. Don't pad it.

Output format

Output the whole PR body inside a single fenced code block so the user can copy and paste it in one action. Nothing outside the code block except a brief note if the Jira ID was missing.

Example
Closes: https://jira.tools.sap/browse/CXSPA-13999

Show the customer's title (e.g. Mr, Ms) on the saved address card so the
displayed name matches what they entered during checkout.

© SAP, Apache-2.0. 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/pr-body of SAP/spartacus.

Open the folder on GitHubat commit 38b4848

Compare with similar skills

PR Body 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 Body compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Body this skillSAP/spartacus784—~499Automated safety check: PassApache-2.0
Acceptance Criteria Checkshopsys/shopsys350—~1kAutomated safety check: PassCustom licence
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Acceptance Criteria Check

    shopsys/shopsys

    Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.

    350 GitHub stars~1k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    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

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

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • 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

  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 3 days ago
    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

More from SAP/spartacus

  • Spartacus Developer

    SAP/spartacus

    Official

    A skill your agent uses for ALL work in a SAP Spartacus (SAP Commerce Cloud composable storefront) Angular application — any storefront feature, component, service, routing, CMS component wiring…

    784 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Schematics

    SAP/spartacus

    Official

    A skill your agent uses when working with Spartacus schematics - Angular schematics for installing, configuring, and migrating Spartacus libraries.

    784 GitHub stars~434 tokensUpdated today
    Auto-check passed

  • Ssr

    SAP/spartacus

    Official

    A skill your agent uses when working with Spartacus Server-Side Rendering (SSR).

    784 GitHub stars~229 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about PR Body

What does PR Body do?

A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch. PR Body is an agent skill from SAP/spartacus, published by the product's own GitHub organization. Use this skill when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.

When should I use PR Body?

PR Body fits situations like: the user asks to generate; draft a pull request (PR) body; description for the current branch; requests like write a PR body.

How do I install PR Body in Claude Code?

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

How do I install PR Body in Codex?

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

Can I use PR Body 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 SAP/spartacus --skill pr-body -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-body, .gemini/skills/pr-body, .github/skills/pr-body and .opencode/skills/pr-body in your project.

What does PR Body need to run?

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

Does PR Body access the network?

SKILL.md names 1 domain. In commands or code: jira.tools.sap; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

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

About 499 tokens (SKILL.md is roughly 2k 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 Body?

Skills that share tags, products or a category with PR Body: Acceptance Criteria Check (shopsys/shopsys, 350 stars), Finishing a Development Branch (obra/superpowers, 296k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Body?

SAP (a GitHub organization, an official publisher) maintains it in SAP/spartacus, which has 784 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.

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