Agent skill

Generate Upgrade Notes

by shopsys in shopsys/shopsys

Generates structured upgrade notes for a pull request based on diff analysis.

Custom licenceAuto-check passedDevelopment

Install Generate Upgrade Notes

skills CLI
$ npx skills add shopsys/shopsys --skill generate-upgrade-notes -a claude-code

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

GitHub CLI
$ gh skill install shopsys/shopsys generate-upgrade-notes --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/shopsys/shopsys.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/generate-upgrade-notes .claude/skills/generate-upgrade-notes && 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
generate-upgrade-notes
GitHub stars
350
Token cost
~2.6k tokens
SKILL.md length
471 words
Files
1
Skills in repo
38
Repo updated
First seen
Licence
Custom licence

At a glance

Generates structured upgrade notes for a pull request based on diff analysis.

  • Works in 5 steps: Resolve Inputs → Fetch PR Data (Using Subagent) → Analyze Changes (Using Subagent) → …
  • Tasks that involve Pull requests
  • SKILL.md covers Initial Setup, Command Arguments and Workflow
  • Calls gh and git

What it does

Generate Upgrade Notes is an agent skill from shopsys/shopsys. Generates structured upgrade notes for a pull request based on diff analysis.

Its SKILL.md is about 2.6k 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: Main repository for maintaining Shopsys Platform packages. Open for ISSUES and PULL REQUESTS.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “Use the generate-upgrade-notes skill to generate structured upgrade notes for a pull request based on diff analysis”
  • “/generate-upgrade-notes”

Workflow steps

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

  1. Resolve Inputs
  2. Fetch PR Data (Using Subagent)
  3. Analyze Changes (Using Subagent)
  4. Generate Upgrade Note Content
  5. Present to User for Review

What it can do on your machine

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

Generate Upgrade Notes loads about 2.6k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 471 words of instructions outside code blocks.

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

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 471 words (~2,633 tokens).

“Generates upgrade notes for Shopsys Platform features when creating pull requests. Analyzes code changes and creates structured upgrade note files following project conventions.”

— opening of SKILL.md by shopsys, Custom licence
name
generate-upgrade-notes

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/generate-upgrade-notes of shopsys/shopsys.

Open the folder on GitHubat commit 3c4bf38

Compare with similar skills

Generate Upgrade Notes 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.

Generate Upgrade Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Generate Upgrade Notes this skillshopsys/shopsys350—~2.6kAutomated safety check: PassCustom licence
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-Anything86k1 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.

    86k 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 shopsys/shopsys

All 38 skills in this repo
  • Adhoc PR

    shopsys/shopsys

    Ad-hoc Pull Request Publisher — commits the current changes, pushes the branch, opens a GitHub pull request against the repository's default branch, and creates a matching SSP Jira issue in the…

    350 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Commit

    shopsys/shopsys

    Interactive commit workflow — analyzes all uncommitted changes, proposes atomic, logically grouped commits with messages following commit-conventions, and executes them only after the user approves…

    350 GitHub stars~771 tokensUpdated today
    Auto-check: notes
  • Create Enum

    shopsys/shopsys

    Create a Shopsys-style enum (a class extending AbstractEnum with public typed constants, NOT a native PHP enum).

    350 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Docs Researcher

    shopsys/shopsys

    Searches and analyzes documentation to provide relevant information for development tasks.

    350 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • PR Comments

    shopsys/shopsys

    Work with GitHub PR review threads — list unresolved comments as a digest (who is waiting on whom), reply to threads, and resolve/unresolve them.

    350 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • PR Description

    shopsys/shopsys

    Generates a PR description focused on business value using the project's PR template.

    350 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Generate Upgrade Notes

What does Generate Upgrade Notes do?

Generates structured upgrade notes for a pull request based on diff analysis. Generate Upgrade Notes is an agent skill from shopsys/shopsys. Generates structured upgrade notes for a pull request based on diff analysis.

When should I use Generate Upgrade Notes?

Generate Upgrade Notes fits situations like: tasks that involve Pull requests.

How do I install Generate Upgrade Notes in Claude Code?

Run `npx skills add shopsys/shopsys --skill generate-upgrade-notes -a claude-code`. Or copy the skill folder (.agents/skills/generate-upgrade-notes in shopsys/shopsys) into .claude/skills/generate-upgrade-notes in your project. Claude Code loads it when a task matches its description.

How do I install Generate Upgrade Notes in Codex?

Run `npx skills add shopsys/shopsys --skill generate-upgrade-notes -a codex`. Or copy the skill folder (.agents/skills/generate-upgrade-notes in shopsys/shopsys) into .agents/skills/generate-upgrade-notes in your project. Codex loads it when a task matches its description.

Can I use Generate Upgrade Notes 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 shopsys/shopsys --skill generate-upgrade-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-upgrade-notes, .gemini/skills/generate-upgrade-notes, .github/skills/generate-upgrade-notes and .opencode/skills/generate-upgrade-notes in your project.

What does Generate Upgrade Notes need to run?

Going by SKILL.md and its folder, Generate Upgrade Notes needs the command-line tools its instructions call (gh and git).

Does Generate Upgrade Notes 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 Generate Upgrade Notes 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 Generate Upgrade Notes use?

Generate Upgrade Notes 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 Generate Upgrade Notes use?

About 2.6k tokens (SKILL.md is roughly 11k 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 Generate Upgrade Notes?

Skills that share tags, products or a category with Generate Upgrade Notes: 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, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Generate Upgrade Notes?

shopsys (a GitHub organization) maintains it in shopsys/shopsys, which has 350 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 7, 2026.

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